[Bug 2083567] Re: mpdscribble when starting as user systemd service
The error goes away after running `sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0` and it can be launched successfully. The value being `1` also stopped the `anki` package from Universe starting. In that case the error was ``` [963029:963029:1003/134821.262544:FATAL:credentials.cc(126)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped) c ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083567 Title: mpdscribble when starting as user systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpdscribble/+bug/2083567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083567] Re: mpdscribble when starting as user systemd service
Sorry that extra `c` at the end is a typo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083567 Title: mpdscribble when starting as user systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpdscribble/+bug/2083567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083567] [NEW] mpdscribble when starting as user systemd service
Public bug reported: When I run `systemctl --user enable --now mpdscribble` it fails. Running `systemctl --user status mpdscribble.service` I see the messages ``` Oct 03 11:54:34 hostname systemd[4560]: Starting mpdscribble.service - AudioScrobbler for MPD... Oct 03 11:54:34 hostname (scribble)[894640]: mpdscribble.service: Failed to set up user namespacing for unprivileged user: Permission denied Oct 03 11:54:34 hostname systemd[4560]: mpdscribble.service: Main process exited, code=exited, status=217/USER Oct 03 11:54:34 hostname systemd[4560]: mpdscribble.service: Failed with result 'exit-code'. Oct 03 11:54:34 hostname systemd[4560]: Failed to start mpdscribble.service - AudioScrobbler for MPD. ``` I think it could be related to https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user- namespaces ``` $ lsb_release -rd No LSB modules are available. Description:Ubuntu 24.04.1 LTS Release:24.04 ``` ``` $ apt-cache policy mpdscribble mpdscribble: Installed: 0.25-2build2 Candidate: 0.25-2build2 Version table: *** 0.25-2build2 500 500 http://nz.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mpdscribble 0.25-2build2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: i3 Date: Thu Oct 3 11:48:34 2024 InstallationDate: Installed on 2023-01-11 (631 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: mpdscribble UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mpdscribble (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083567 Title: mpdscribble when starting as user systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpdscribble/+bug/2083567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] Re: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
@mruffell my change has been pulled into the latest stable 5.4 and 5.15 kernel queues: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/tree/queue-5.4/tcp-check-skb-is-non-null-in- tcp_rto_delta_us.patch https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/tree/queue-5.15/tcp-check-skb-is-non-null-in- tcp_rto_delta_us.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077657 Title: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083255] [NEW] Restore erofs.ko to linux-modules
Public bug reported: Similar to https://bugs.launchpad.net/ubuntu/+source/linux- azure/+bug/2081613 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809, erofs.ko is missing from linux-aws. A fix has already been accepted to linux-azure: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- azure/+git/jammy/commit/?id=c7fec922603a7ff52bd037f6ce6791b08f1cfaef Can we get this into linux-aws as well? Thanks. ** Affects: linux-aws (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/2083255 Title: Restore erofs.ko to linux-modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2083255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] Re: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
Thanks @mruffell. No, we're not running a custom kernel. We've just disabled the 2 sysctsl I mentioned, tcp_early_retrans and tcp_recovery, for now to mitigate the issue. I just checked and it looks like my change applies cleanly to the HEAD of focal. I think we'd like to see it applied to both 5.4 and 5.15. Please let me know if there is a problem applying it to either when you get to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077657 Title: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] Re: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
My mitigation was accepted upstream: https://lore.kernel.org/netdev/172708862651.3320223.2618494280244639290.git- patchwork-not...@kernel.org/ @mruffell I believe this should be picked up by the stable maintainers. Do you know how long it will take once it lands there until it's in an official Ubuntu kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077657 Title: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080540] [NEW] Yoga 9i 2in1 left click shows left click in lib-input but system registers as right click 80% of the time.
Public bug reported: sudo libinput debug-events -event11 DEVICE_ADDEDVideo Bus seat0 default group1 cap:k -event1 DEVICE_ADDEDPower Button seat0 default group2 cap:k -event0 DEVICE_ADDEDLid Switchseat0 default group3 cap:S -event2 DEVICE_ADDEDSleep Button seat0 default group4 cap:k -event4 DEVICE_ADDEDELAN06FA:00 04F3:3293 Mouse seat0 default group5 cap:p left scroll-nat scroll-button -event5 DEVICE_ADDEDELAN06FA:00 04F3:3293 Touchpadseat0 default group5 cap:pg size 134x78mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on dwtp-on -event6 DEVICE_ADDEDWacom HID 53A6 Penseat0 default group6 cap:T size 302x189mm left calib -event7 DEVICE_ADDEDWacom HID 53A6 Finger seat0 default group6 cap:t size 302x189mm ntouches 10 calib -event9 DEVICE_ADDEDIdeapad extra buttons seat0 default group7 cap:k -event8 DEVICE_ADDEDIntel HID events seat0 default group8 cap:k -event10 DEVICE_ADDEDLenovo Yoga Tablet Mode Control switch seat0 default group9 cap:S -event3 DEVICE_ADDEDAT Translated Set 2 keyboard seat0 default group10 cap:k -event5 POINTER_BUTTON +0.011s BTN_LEFT (272) pressed, seat count: 1 event5 POINTER_BUTTON +0.122s BTN_LEFT (272) released, seat count: 0 event5 POINTER_BUTTON +3.895s BTN_LEFT (272) pressed, seat count: 1 event5 POINTER_BUTTON +4.000s BTN_LEFT (272) released, seat count: 0 event5 POINTER_BUTTON +4.474s BTN_LEFT (272) pressed, seat count: 1 event5 POINTER_BUTTON +4.550s BTN_LEFT (272) released, seat count: 0 -event3 KEYBOARD_KEY+5.580s *** (-1) pressed event3 KEYBOARD_KEY+5.797s *** (-1) pressed ^C cat system_info.txt System Information: Linux darkleblue 6.10.9-061009-generic #202409080636 SMP PREEMPT_DYNAMIC Sun Sep 8 07:46:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux CPU Info: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes:46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 22 On-line CPU(s) list: 0-21 Vendor ID:GenuineIntel Model name: Intel(R) Core(TM) Ultra 7 155H CPU family: 6 Model:170 Thread(s) per core: 2 Core(s) per socket: 16 Socket(s):1 Stepping: 4 CPU(s) scaling MHz: 30% CPU max MHz: 4800. CPU min MHz: 400. BogoMIPS: 5990.40 Flags:fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb intel_ppin ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid bus_lock_detect movdiri movdir64b fsrm md_clear serialize arch_lbr ibt flush_l1d arch_capabilities Virtualization: VT-x NUMA node(s): 1 NUMA node0 CPU(s):0-21 Vulnerability Gather data sampling: Not affected Vulnerability Itlb multihit: Not affected Vulnerability L1tf: Not affected Vulnerability Mds:Not affected Vulnerability Meltdown: Not affected Vulnerability Mmio stale data:Not affected Vulnerability Reg file data sampling: Not affected Vulnerability Retbleed: Not affected Vulnerability Spec rstack overflow: Not affected Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; Enhanced / Automatic IBRS; IBPB conditional;
[Bug 2078511] [NEW] Unable to reduce column width for file NAME in nautilus
Public bug reported: In Nautilus, I'm unable to shrink the width of the Name column. I can increase it, but the default wide value is the minimum size. And it's really wide. And none of the filenames are long. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.2-0ubuntu0.2 Uname: Linux 6.10.6-061006-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 14:43:40 2024 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'date_modified', 'date_accessed', 'date_created', 'recency', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2024-08-28 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screenshot from 2024-08-30 14-46-30.png" https://bugs.launchpad.net/bugs/2078511/+attachment/5811194/+files/Screenshot%20from%202024-08-30%2014-46-30.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078511 Title: Unable to reduce column width for file NAME in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2078511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077021] Re: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2: nvidia kernel module failed to build
I noticed that this only happened to me when I unplugged my monitor from my GTX 970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077021 Title: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2077021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077837] Re: unable to access fingerprint device after suspend/resume
Opened an upstream issue too. https://gitlab.gnome.org/GNOME/gnome- control-center/-/issues/3166 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #3166 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3166 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077837 Title: unable to access fingerprint device after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077837] [NEW] unable to access fingerprint device after suspend/resume
Public bug reported: After suspending and then resuming during the fingerprint registration process, the finerprint device will be unable to be accessed. However, use fprint-enroll to register fingerprint on the command line, the fingerprint device can operate normally. I have to restart the system to register fingerprint from setting UI again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 26 11:35:45 2024 InstallationDate: Installed on 2022-11-23 (641 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot from 2024-08-26 11-12-03.png" https://bugs.launchpad.net/bugs/2077837/+attachment/5809238/+files/Screenshot%20from%202024-08-26%2011-12-03.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077837 Title: unable to access fingerprint device after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2077837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] Re: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
07:26:16 rx [1006006.580040] RAX: 8ed08b20 RBX: 0005
RCX: 0001
Aug 7 07:26:16 rx [1006006.587337] RDX: f48eeca2 RSI: 0082
RDI: 0082
Aug 7 07:26:16 rx [1006006.594635] RBP: b42600177e90 R08:
R09: 020f
Aug 7 07:26:16 rx [1006006.601931] R10: 0010 R11:
R12: 0005
Aug 7 07:26:16 rx [1006006.609229] R13: 93157deb5f00 R14:
R15:
Aug 7 07:26:16 rx [1006006.616530] ? __cpuidle_text_start+0x8/0x8
Aug 7 07:26:16 rx [1006006.620886] ? default_idle+0x20/0x140
Aug 7 07:26:16 rx [1006006.624804] arch_cpu_idle+0x15/0x20
Aug 7 07:26:16 rx [1006006.628545] default_idle_call+0x23/0x30
Aug 7 07:26:16 rx [1006006.632640] do_idle+0x1fb/0x270
Aug 7 07:26:16 rx [1006006.636035] cpu_startup_entry+0x20/0x30
Aug 7 07:26:16 rx [1006006.640126] start_secondary+0x178/0x1d0
Aug 7 07:26:16 rx [1006006.644218] secondary_startup_64+0xa4/0xb0
Aug 7 07:26:17 rx [1006006.648568] Modules linked in: vrf bridge stp llc vxlan
ip6_udp_tunnel udp_tunnel nls_iso8859_1 nft_ct amd64_edac_mod edac_mce_amd
kvm_amd kvm crct10dif_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd
glue_helper wmi_bmof ipmi_ssif input_leds joydev rndis_host cdc_ether usbnet
ast mii drm_vram_helper ttm drm_kms_helper i2c_algo_bit fb_sys_fops syscopyarea
sysfillrect sysimgblt ccp mac_hid ipmi_si ipmi_devintf ipmi_msghandler
sch_fq_codel nf_tables_set nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables
nfnetlink ramoops reed_solomon efi_pstore drm ip_tables x_tables autofs4 raid10
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq
libcrc32c raid0 multipath linear mlx5_ib ib_uverbs ib_core raid1 hid_generic
mlx5_core pci_hyperv_intf crc32_pclmul usbhid ahci tls mlxfw bnxt_en hid
libahci nvme i2c_piix4 nvme_core wmi [last unloaded: cpuid]
Aug 7 07:26:17 rx [1006006.726180] CR2: 0020
Aug 7 07:26:17 rx [1006006.729718] ---[ end trace e0e2e37e4e612984 ]---
Also the proposed "workaround" patch I pasted in the original writeup is
not correct. I think something like the following may be more
appropriate:
Author: Josh Hunt
Date: Tue Jul 30 19:45:43 2024 -0400
tcp: check skb is non-NULL before using in tcp_rto_delta_us()
There have been multiple occassions where we have crashed in this path
because
packets_out suggested there were packets on the write or retransmit queues,
but in fact there weren't leading to a NULL skb being dereferenced. While
we
should fix that root cause we should also just make sure the skb is not NULL
before dereferencing it. Also add a warn once here to capture some
information
if/when the problem case is hit again.
Signed-off-by: Josh Hunt
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 2aac11e7e1cc..932f0de641e4 100644
--- a/include/net/tcp.h
+++ b/include/net/tcp.h
@@ -2434,9 +2434,18 @@ static inline s64 tcp_rto_delta_us(const struct sock *sk)
{
const struct sk_buff *skb = tcp_rtx_queue_head(sk);
u32 rto = inet_csk(sk)->icsk_rto;
- u64 rto_time_stamp_us = tcp_skb_timestamp_us(skb) +
jiffies_to_usecs(rto);
- return rto_time_stamp_us - tcp_sk(sk)->tcp_mstamp;
+ if (likely(skb)) {
+ u64 rto_time_stamp_us = tcp_skb_timestamp_us(skb) +
jiffies_to_usecs(rto);
+
+ return rto_time_stamp_us - tcp_sk(sk)->tcp_mstamp;
+ } else {
+ WARN_ONCE(1,
+ "rtx queue emtpy: inflight %u tlp_high_seq %u state
%u\n",
+ tcp_sk(sk)->packets_out, tcp_sk(sk)->tlp_high_seq,
sk->sk_state);
+ return jiffies_to_usecs(rto);
+ }
+
}
/*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077657
Title:
Kernel Oops - BUG: kernel NULL pointer dereference, RIP:
0010:tcp_rearm_rto+0xe4/0x160
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] Re: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+attachment/5808086/+files/uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077657 Title: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] Re: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+attachment/5808087/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077657 Title: Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077657] [NEW] Kernel Oops - BUG: kernel NULL pointer dereference, RIP: 0010:tcp_rearm_rto+0xe4/0x160
OUT ||
icsk->icsk_pending == ICSK_TIME_LOSS_PROBE) {
s64 delta_us = tcp_rto_delta_us(sk);
As mentioned earlier there seems to be a problem with the packets_out
accounting here still which causes the kernel to think there are either
still packets in the write or retransmit queues. Additionally I feel
like we should probably add a patch in tcp_rto_delta_us() to check that
the skb is non-null b/f trying to read the timestamp. Possibly something
like this:
Author: Josh Hunt
Date: Tue Jul 30 19:45:43 2024 -0400
workaround empty rtx queue
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 2aac11e7e1cc..d1e2ecbce536 100644
--- a/include/net/tcp.h
+++ b/include/net/tcp.h
@@ -2434,7 +2434,8 @@ static inline s64 tcp_rto_delta_us(const struct sock *sk)
{
const struct sk_buff *skb = tcp_rtx_queue_head(sk);
u32 rto = inet_csk(sk)->icsk_rto;
- u64 rto_time_stamp_us = tcp_skb_timestamp_us(skb) +
jiffies_to_usecs(rto);
+ u64 rto_time_stamp_us = skb ? tcp_skb_timestamp_us(skb) : 0 +
jiffies_to_usecs(rto);
+ WARN_ON_ONCE(!skb);
return rto_time_stamp_us - tcp_sk(sk)->tcp_mstamp;
}
I tried looking to see if there are any new commits upstream either in
Ubuntu's 5.4 kernels or upstream's net-next branch which could resolve
this problem, but did not find anything. We've also tried reproducing
this in a lab environment without success so far.
Please let me know if you need any other information to help root cause
this issue.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: kernel-oops
** Attachment added: "version signature"
https://bugs.launchpad.net/bugs/2077657/+attachment/5808085/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077657
Title:
Kernel Oops - BUG: kernel NULL pointer dereference, RIP:
0010:tcp_rearm_rto+0xe4/0x160
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
Reported upstream at https://bugzilla.kernel.org/show_bug.cgi?id=219101 . ** Bug watch added: Linux Kernel Bug Tracker #219101 https://bugzilla.kernel.org/show_bug.cgi?id=219101 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073625] [NEW] systemd-nspawn uses cgroupv1
Public bug reported: Even though Ubuntu 22.04 is definitely using cgroup2: cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) systemd appears to be using cgroup: cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc) When starting a container using default configuration from `systemd-nspawn@` unit it automatically selects cgroupv1 for some reason: systemd-nspawn@debian-sid.service - Container debian-sid Loaded: loaded (/lib/systemd/system/systemd-nspawn@.service; disabled; vendor preset: enabled) Active: active (running) since Sat 2024-07-20 00:48:30 +07; 1s ago Docs: man:systemd-nspawn(1) Main PID: 5210 (systemd-nspawn) Status: "Container running." Tasks: 2 (limit: 16384) Memory: 2.7M CGroup: /machine.slice/systemd-nspawn@debian-sid.service ├─payload │ └─5214 /usr/lib/systemd/systemd └─supervisor └─5210 systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth -U --settings=override --ma> ก.ค. 20 00:48:30 ubuntu-dev systemd[1]: Starting Container debian-sid... ก.ค. 20 00:48:30 ubuntu-dev systemd[1]: Started Container debian-sid. ก.ค. 20 00:48:30 ubuntu-dev systemd-nspawn[5210]: Legacy cgroup v1 support selected. This is no longer supported ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-container 249.11-0ubuntu3.12 ProcVersionSignature: Ubuntu 6.5.0-44.44~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 20 00:43:45 2024 InstallationDate: Installed on 2024-07-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2073625 Title: systemd-nspawn uses cgroupv1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2073625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073238] [NEW] Kernel Panic on Ubuntu Server 22.04.4 with 5.15.0-113-generic Kernel and Intel QAT Driver
Public bug reported: I am experiencing a kernel panic issue on Ubuntu Server 22.04.4 with the 5.15.0-113-generic kernel. The server freezes during boot, and the kernel log shows an Oops error (0002) followed by a workqueue event error related to the Intel QuickAssist Technology (QAT) driver. The log indicates that the issue occurs in the function "write_csr_ring_config" within the "intel_qat" module. -- [ 48.266348] BUG: unable to handle page fault for address: 00101000 [ 48.269005] #PF: supervisor write access in kernel mode [ 48.271653] #PF: error_code(0x0002) - not-present page [ 48.274298] PGD 2ae946067 P4D 0 [ 48.276919] Oops: 0002 [#1] SMP NOPTI [ 48.279528] CPU: 0 PID: 2413 Comm: kworker/0:3 Not tainted 5.15.0-113-generic #123-Ubuntu [ 48.282262] Hardware name: Intel Corporation ArcherCityM/ArcherCityM, BIOS 5.32 06/04/2024 [ 48.285053] Workqueue: events work_for_cpu_fn [ 48.287834] RIP: 0010:write_csr_ring_config+0x1a/0x30 [intel_qat] [ 48.290677] Code: 00 48 89 e5 8b 00 5d c3 cc cc cc cc 0f 1f 40 00 0f 1f 44 00 00 55 c1 e2 02 c1 e6 0d 48 8d 84 32 00 10 10 00 48 01 c7 48 89 e5 <89> 0f 5d c3 cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 [ 48.299285] RSP: 0018:ff5c5439751c7cd0 EFLAGS: 00010206 [ 48.302224] RAX: 00101000 RBX: ff235071209cc000 RCX: [ 48.305216] RDX: RSI: RDI: 00101000 [ 48.308195] RBP: ff5c5439751c7cd0 R08: R09: [ 48.311167] R10: 000a R11: 0006 R12: [ 48.314118] R13: R14: ff23507273b7d828 R15: 0001 [ 48.317053] FS: () GS:ff2350ee3f00() knlGS: [ 48.320021] CS: 0010 DS: ES: CR0: 80050033 [ 48.322962] CR2: 00101000 CR3: 000125f0e003 CR4: 00771ef0 [ 48.325958] DR0: DR1: DR2: [ 48.328904] DR3: DR6: fffe07f0 DR7: 0400 [ 48.331797] PKRU: 5554 [ 48.334650] Call Trace: [ 48.337465] [ 48.340228] ? show_trace_log_lvl+0x1d6/0x2ea [ 48.342995] ? show_trace_log_lvl+0x1d6/0x2ea [ 48.345693] ? adf_init_bank+0x117/0x340 [intel_qat] [ 48.348383] ? show_regs.part.0+0x23/0x29 [ 48.351052] ? __die_body.cold+0x8/0xd [ 48.353722] ? __die+0x2b/0x37 [ 48.356340] ? page_fault_oops+0x13b/0x170 [ 48.358948] ? do_user_addr_fault+0x321/0x670 [ 48.361516] ? __cond_resched+0x1a/0x50 [ 48.364045] ? exc_page_fault+0x77/0x170 [ 48.364050] ? asm_exc_page_fault+0x27/0x30 [ 48.368879] ? write_csr_ring_config+0x1a/0x30 [intel_qat] [ 48.368891] adf_init_bank+0x117/0x340 [intel_qat] [ 48.368903] ? d_instantiate+0x44/0x60 [ 48.368910] adf_init_etr_data+0xe6/0x170 [intel_qat] [ 48.368921] adf_dev_init+0x2f/0x160 [intel_qat] [ 48.368969] adf_probe+0x332/0x3c0 [qat_4xxx] [ 48.369021] local_pci_probe+0x48/0x90 [ 48.369027] work_for_cpu_fn+0x17/0x30 [ 48.369030] process_one_work+0x228/0x3d0 [ 48.369034] worker_thread+0x223/0x420 [ 48.369037] ? process_one_work+0x3d0/0x3d0 [ 48.369042] kthread+0x127/0x150 [ 48.369047] ? set_kthread_struct+0x50/0x50 [ 48.369051] ret_from_fork+0x1f/0x30 [ 48.369059] [ 48.369060] Modules linked in: snd_pcm qat_4xxx(+) isst_if_mbox_pci(+) pmt_telemetry intel_qat idxd(+) isst_if_mmio(+) snd_timer pmt_crashlog isst_if_common pmt_class authenc idxd_bus irdma(+) snd mei_me soundcore mei joydev input_leds cdc_subset ast(-) fjes(-) ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler cxl_acpi cxl_core mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib ib_uverbs ib_core cdc_ether usbnet mii hid_generic usbhid uas hid usb_storage nouveau mlx5_core mxm_wmi drm_vram_helper i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper sha256_ssse3 sha1_ssse3 syscopyarea aesni_intel crypto_simd sysfillrect cryptd mlxfw sysimgblt psample fb_sys_fops mpt3sas cec i2c_i801 rc_core [ 48.403214] raid_class tls video nvme xhci_pci intel_pmt pci_hyperv_intf ice i40e drm scsi_transport_sas wmi nvme_core i2c_smbus i2c_ismt xhci_pci_renesas pinctrl_emmitsburg [ 48.403362] CR2: 00101000 [ 48.403375] ---[ end trace 34334d80c317be6f ]--- [ 48.642146] RIP: 0010:write_csr_ring_config+0x1a/0x30 [intel_qat] [ 48.645234] Code: 00 48 89 e5 8b 00 5d c3 cc cc cc cc 0f 1f 40 00 0f 1f 44 00 00 55 c1 e2 02 c1 e6 0d 48 8d 84 32 00 10 10 00 48 01 c7 48 89 e5 <89> 0f 5d c3 cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 [ 48.654898] RSP: 0018:ff5c5439751c7cd0 EFLAGS: 00010206 [ 48.658210] RAX: 001010
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
The problem happened again with 6.10-rc4 kernel. uname output, kern.log, and dmesg output attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
** Attachment added: "6_10_rc4_dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+attachment/5796804/+files/6_10_rc4_dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
** Attachment added: "6_10_rc4_kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+attachment/5796803/+files/6_10_rc4_kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
** Attachment added: "6_10_rc4_uname.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+attachment/5796802/+files/6_10_rc4_uname.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072819] Re: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
It is a QEMU virtual machine but the original installation was done with the official Ubuntu Desktop ISO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072819 Title: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2072819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072819] [NEW] package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
Public bug reported: I was doing a do-release-update -d to 24.04 from 22.04. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: grub-efi-amd64-signed 1.202+2.12-1ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13 Uname: Linux 6.5.0-41-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 11 21:04:18 2024 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-25 (230 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-07-12 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-23T06:30:10 ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072819 Title: package grub-efi-amd64-signed 1.202+2.12-1ubuntu7 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/2072819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
Firmware was already updated (verified both with fwupdmgr and by booting into Windows and using Lenovo tools). I will work on installing a mainline kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
Possibly related: https://bbs.archlinux.org/viewtopic.php?id=295939 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] Re: Lenovo touchpad intermittently stops working with i2c_designware errors
** Description changed: Hi. When using my laptop, I frequently experience the touchpad suddenly cease working. Sometimes there's a few seconds' warning with reduced responsiveness, and sometimes it's completely sudden. I experienced this in Kubuntu 22.04, and I still experience it after upgrading to 24.04. Output from kern.log when it happens often looks like this: 2024-07-09T21:31:51.573862-04:00 machinename kernel: i2c_designware AMDI0010:00: controller timed out 2024-07-09T21:31:51.577113-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout in disabling adapter 2024-07-09T21:31:51.596828-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout waiting for bus ready 2024-07-09T21:32:45.928870-04:00 machinename kernel: message repeated 2652 times: [ i2c_designware AMDI0010:00: timeout waiting for bus ready] The only workaround I've found is to sleep/hibernate or shut down the laptop; it always works again on reboot. Since I upgraded to 24.04, I - have the additional problem that I can't sleep the laptop when this is - happening. I get errors that say "kernel: Lockdown: systemd-logind: - hibernation is restricted; see man kernel_lockdown.7" when I try. + sometimes have the additional problem that I can't sleep the laptop when + this is happening. I get errors that say "kernel: Lockdown: systemd- + logind: hibernation is restricted; see man kernel_lockdown.7" when I + try. Note that the problem did not happen between my most recent boot and the generation of the attached files via "ubuntu-bug linux". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-36-generic 6.8.0-36.36 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jul 9 22:02:03 2024 InstallationDate: Installed on 2021-11-28 (954 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82ND ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=1ae6eb8d-78a6-4fdd-affc-4d1e32c995d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-6.8.0-36-generic N/A - linux-backports-modules-6.8.0-36-generic N/A - linux-firmware20240318.git3b128b60-0ubuntu2.1 + linux-restricted-modules-6.8.0-36-generic N/A + linux-backports-modules-6.8.0-36-generic N/A + linux-firmware20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-06-27 (12 days ago) dmi.bios.date: 03/26/2024 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: H6CN22WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ALC6 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrH6CN22WW(V1.15):bd03/26/2024:br1.22:efr1.22:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6: dmi.product.family: Yoga 6 13ALC6 dmi.product.name: 82ND dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6 dmi.product.version: Yoga 6 13ALC6 dmi.sys.vendor: LENOVO modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072612] [NEW] Lenovo touchpad intermittently stops working with i2c_designware errors
Public bug reported: Hi. When using my laptop, I frequently experience the touchpad suddenly cease working. Sometimes there's a few seconds' warning with reduced responsiveness, and sometimes it's completely sudden. I experienced this in Kubuntu 22.04, and I still experience it after upgrading to 24.04. Output from kern.log when it happens often looks like this: 2024-07-09T21:31:51.573862-04:00 machinename kernel: i2c_designware AMDI0010:00: controller timed out 2024-07-09T21:31:51.577113-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout in disabling adapter 2024-07-09T21:31:51.596828-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout waiting for bus ready 2024-07-09T21:32:45.928870-04:00 machinename kernel: message repeated 2652 times: [ i2c_designware AMDI0010:00: timeout waiting for bus ready] The only workaround I've found is to sleep/hibernate or shut down the laptop; it always works again on reboot. Since I upgraded to 24.04, I have the additional problem that I can't sleep the laptop when this is happening. I get errors that say "kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" when I try. Note that the problem did not happen between my most recent boot and the generation of the attached files via "ubuntu-bug linux". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-36-generic 6.8.0-36.36 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jul 9 22:02:03 2024 InstallationDate: Installed on 2021-11-28 (954 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82ND ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=1ae6eb8d-78a6-4fdd-affc-4d1e32c995d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-36-generic N/A linux-backports-modules-6.8.0-36-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-06-27 (12 days ago) dmi.bios.date: 03/26/2024 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: H6CN22WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ALC6 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrH6CN22WW(V1.15):bd03/26/2024:br1.22:efr1.22:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6: dmi.product.family: Yoga 6 13ALC6 dmi.product.name: 82ND dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6 dmi.product.version: Yoga 6 13ALC6 dmi.sys.vendor: LENOVO modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
Re # 65, I've tested and even created a video showing people how to install and test it as well . Thanks, for this fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067103] [NEW] Plasma desktop on 24.04 resizes after monitor goes to sleep and wakes up
Public bug reported: Description:Ubuntu 24.04 LTS Release:24.04 plasma-desktop: Installed: 4:5.27.11-0ubuntu2 Candidate: 4:5.27.11-0ubuntu2 Version table: *** 4:5.27.11-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages 100 /var/lib/dpkg/status What happens: When the monitor of the desktop is turned off and on again, the plasma desktop (background and panels and widgets) are resized and reduced to the top left corner of the screen. The other windows remain in the same place. What should happen: When the monitor is toggled off and then on, plasma desktop should not resize anything and everything should remain in place where it was when the monitor was turned off. I have confirmed this with two separate nvidia drivers (470 and 550). I can also confirm this bug does not exist in 23.10. To reproduce on 24.04 I turn off my desktop monitor and then turn it back on. When it is turned back on the plasma desktop background and top panel are reduced to a corner of my screen but the other windows I have open remain in the same place. In other words, the desktop resolution is not changing, but plasma is resizing. I can confirm that killing plasmashell and restarting causes the plasma desktop to be resized properly. Running: ``` killall plasmashell kstart plasmashell ``` will restore plasma desktop to the right size of the full monitor resolution. I can also confirm that this happens when the monitor goes to sleep. It does not happen when the screen is locked. It only apears to happen when the monitor goes to sleep or is turned off. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: plasma-desktop 4:5.27.11-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 24 09:15:06 2024 InstallationDate: Installed on 2024-03-15 (71 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: plasma-desktop UpgradeStatus: Upgraded to noble on 2024-05-23 (2 days ago) ** Affects: plasma-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "plasma-resized-after-monitor-shutoff-2024-05-24_09-23.png" https://bugs.launchpad.net/bugs/2067103/+attachment/5782277/+files/plasma-resized-after-monitor-shutoff-2024-05-24_09-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067103 Title: Plasma desktop on 24.04 resizes after monitor goes to sleep and wakes up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/2067103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066526] [NEW] Filezilla crashes when uploading files
Public bug reported: After upgrading from Ubuntu 23.10 to 24.04, I am no longer able to upload files using filezilla. The program leaves a zero-sized placeholder on the remote server, then crashes with a generic core dump message. See also: https://forum.filezilla-project.org/viewtopic.php?t=58592 As reported there, the latest pre-built upstream release works as expected, but that is only really relevant insofar as it provides affected users with a viable/temporary workaround. Description:Ubuntu 24.04 LTS Release:24.04 filezilla: Installed: 3.66.5-2build2 Candidate: 3.66.5-2build2 ** Affects: filezilla (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/2066526 Title: Filezilla crashes when uploading files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/filezilla/+bug/2066526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060331] Re: add-apt-repository --list not returning any deb822 repositories
In case anyone else comes across this bug, the following workaround to
create the old style '.list' file works well:
---
1. Create an 'aptaddppa' function (ZSH):
---
aptaddppa () {
curl -fsSL
"https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x${4}"; | sudo
gpg --dearmor -o /etc/apt/trusted.gpg.d/"${1}".gpg
echo "deb [arch=$(dpkg --print-architecture)] ${2} $(lsb_release
-cs) ${3}" | sudo tee /etc/apt/sources.list.d/"${1}".list
sudo apt update
}
---
2. From the command line:
---
$ aptaddppa flacon https://ppa.launchpadcontent.net/flacon/ppa/ubuntu
main 0606FBEA73863686801BE20ED5790E4FF2A61FE5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060331
Title:
add-apt-repository --list not returning any deb822 repositories
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060331] [NEW] add-apt-repository --list not returning any deb822 repositories
Public bug reported: Recreating the following bug report (#2052851) with a new title per Jeremy Bícha's (jbicha) request: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2052851 --- On Ubuntu 23.10: * When adding a PPA, 'add-apt-repository' will add the repository in the new deb822 format as a '.sources' file in '/etc/apt/sources.list.d' * However, 'add-apt-repository --list' cannot see/understand the new '.sources' file For example, with the flacon ppa (https://launchpad.net/~flacon/+archive/ubuntu/ppa): 1. 'sudo add-apt-repository ppa:flacon/ppa' adds the flacon repo as '/etc/apt/sources.list.d/flacon-ubuntu-ppa-mantic.sources' 2. apt can install and update from the new repo, as expected. you can also remove the repo, as expected, by running 'sudo add-apt-repository --remove ppa:flacon/ppa' 3. However, 'add-apt-repository --list' does not list the repo as it should. GUI package managers such as Muon and Synaptic also do not see the new repo. It makes working with packages frustrating, and unfortunately, per Julian Andres Klode (juliank), there seems to be no plan to fix the broken 'software-properties-common' any time soon. See here: https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/2033949 Also see related issues: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761 https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037210 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2036288 https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042791.html ** Affects: software-properties (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/2060331 Title: add-apt-repository --list not returning any deb822 repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2060331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
Yep I'll have to do a fresh install though since I've already gone and configured it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
Yeah it showed 127.0.0.1.53. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
I'll have to double check but I'm pretty sure it showed 127.0.0.1.53 (localhost). Not my DNS servers or the DNS servers entered into the GUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
Hi Seth, I am using the GUI built into the desktop - the one in the top right where I can turn bluetooth on/off and change wifi networks. Toggling the DNS Server section from automatic to off did not result in the DNS server entered being used. Additionally using nslookup didn't result in a response until a request was made by a web browser. https://gyazo.com/1e33fa49040bf14afbbd99252dc37993 https://gyazo.com/75d3cdd0e4412166e807375f784fc305 https://gyazo.com/7617efb2e8d7f89dc0c2f3ceec6c3109 Thanks, Josh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966100] [NEW] getaddrinfo not fork-safe
Public bug reported:
When compiling the following code and executing the program, the child
process hangs forever on a mutex that was held by `getaddrinfo` on
another thread at the time of the fork. I don't see anything in the
manpage for `getaddrinfo` that suggests this shouldn't work. I suspect
glibc is missing a call to `pthread_atfork`.
mre.cpp
```
#include
#include
#include
void spamGetaddrinfo()
{
for (int i = 0; i< 100; ++i)
{
addrinfo *addrInfo{nullptr};
::getaddrinfo("google.com", "80", nullptr, &addrInfo);
}
printf("Thread is done\n");
}
int main()
{
auto thread = std::thread{spamGetaddrinfo};
usleep(1);
if (auto pid = fork(); pid != 0)
{
// Parent
printf("Parent is done\n");
thread.join();
}
else
{
// Child
addrinfo *addrInfo{nullptr};
::getaddrinfo("google.com", "80", nullptr, &addrInfo);
printf("Child is done\n");
}
}
```
Run `g++ -std=c++17 -pthread mre.cpp && ./a.out`
Expected output:
```
Parent is done
Child is done
Thread is done
```
Actual output:
```
Parent is done
Thread is done
```
When finished, use `pkill a.out` to remove the leftover child process.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libc6 2.27-3ubuntu1.5
ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
Uname: Linux 4.15.0-166-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
Date: Wed Mar 23 10:32:43 2022
Dependencies:
gcc-8-base 8.4.0-1ubuntu1~18.04
libc6 2.27-3ubuntu1.5
libgcc1 1:8.4.0-1ubuntu1~18.04
InstallationDate: Installed on 2019-12-07 (836 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
ProcEnviron:
LANG=en_US.UTF-8
TERM=screen
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, user)
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966100
Title:
getaddrinfo not fork-safe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1966100/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955743] [NEW] Ubuntu rocks! except when the installation...
Public bug reported: not applicable. i did not create ubuntu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 Date: Sat Dec 25 11:23:33 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu ** Attachment added: "Screenshot from 2021-12-25 11-23-19.png" https://bugs.launchpad.net/bugs/1955743/+attachment/5549546/+files/Screenshot%20from%202021-12-25%2011-23-19.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955743 Title: Ubuntu rocks! except when the installation... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1955743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946222] [NEW] presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' in the 'linux-firmware' package causes Intel AX210 wifi to cease functioning
Public bug reported: When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' exists (after a fresh OS installation & after updates to the 'linux-firmware' package)--wifi fails to function: $ lspci -knn | grep Net -A3 93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:4020] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep iwlwifi [2.390962] iwlwifi :93:00.0: enabling device ( -> 0002) [2.412571] iwlwifi :93:00.0: api flags index 2 larger than supported by driver [2.412585] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [2.412827] iwlwifi :93:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [2.433308] iwlwifi :93:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [2.582482] iwlwifi :93:00.0: loaded PNVM version 0x324cd670 [2.830634] iwlwifi :93:00.0: Timeout waiting for PNVM load! [2.830639] iwlwifi :93:00.0: Failed to start RT ucode: -110 [2.830643] iwlwifi :93:00.0: iwl_trans_send_cmd bad state = 1 [3.034634] iwlwifi :93:00.0: firmware didn't ACK the reset - continue anyway [3.046824] iwlwifi :93:00.0: Failed to run INIT ucode: -110 When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' is deleted, or renamed-- wifi works: $ lspci -knn | grep Net -A3 93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:4020] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep iwlwifi [3.425668] iwlwifi :93:00.0: enabling device ( -> 0002) [3.436377] iwlwifi :93:00.0: api flags index 2 larger than supported by driver [3.436392] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [3.436634] iwlwifi :93:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [3.459053] iwlwifi :93:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [3.698849] iwlwifi :93:00.0: base HW address: a0:e7:0b:5a:ec:77 [3.716331] iwlwifi :93:00.0 wlp147s0: renamed from wlan0 --1-- $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 --2-- $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.17 Candidate: 1.187.17 Version table: *** 1.187.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages --3-- Expectation: Intel AX210 wifi works without having to perform extra steps to rename/delete files after linux-firmware package updates --4-- Reality: Intel AX210 wifi does not work without performing extra steps to rename/delete files after linux-firmware package updates I have no idea where the .pnvm file is coming from as it is not present in the files provided by Intel at https://www.intel.com/content/www/us/en/support/articles/05511/wireless.html Please consider removing the .pnvm files from all versions of the 'linux-firmware' package... currently found in these versions: 1 pnvm file - https://packages.ubuntu.com/focal-updates/all/linux- firmware/filelist 2 pnvm files - https://packages.ubuntu.com/impish/all/linux- firmware/filelist The pnvm file is not present in the Ubuntu 2104 (Hirsute) linux-firmware package and the AX210 wifi works perfectly well on that platform but it fails to function on 20.04 (Focal), where the pnvm is present, and will likely also fail in 21.10 (Impish). ** Affects: linux-firmware (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/1946222 Title: presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' in the 'linux- firmware' package causes Intel AX210 wifi to cease functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1946222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
FWIW, I have a pretty consistent reproduction of this on my 20.04 machine here. Restarting gnome-shell with Alt-F2 then "r" causes all the window management stuff to go away, but doesn't actually kill the process that's reporting the giant resident set size. Manually killing that pid also causes the WM chrome to disappear for a second and then pop back once a new gnome-shell process spawns. That one comes up almost instantly with a huge (but smaller, at least) RSS: 0] jbm@complexity:~/Downloads $ ps l 650626 F UID PIDPPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 0 1000 6506262554 20 0 6884676 2449912 - Rsl ? 62:14 /usr/bin/gnome-shell 0] jbm@complexity:~/Downloads $ kill 650626 (run top to get the new PID) 130] jbm@complexity:~/Downloads $ ps l 665168 F UID PIDPPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 0 1000 6651682554 20 0 6248912 1988284 poll_s Ssl ?0:57 /usr/bin/gnome-shell So, it's gone from 2449912 to 1988284. That isn't nothing: 2.3GiB vs 1.9GiB, but it's still a heck of a lot of RAM for a newly-spawned process. Hope this report helps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 908791] Re: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja-Dup launch place
a few years later, i am still seeing this issue running as a normal (non-root) user w/most recent pkgs for 16.04.3LTS. gvfs-backends was not installed automatically w/deja-dup pkg installed today (almost 10yr after this issue was opened). i located this ticket via this post, figured i'd let you know it's still out there. https://askubuntu.com/questions/459679/deja-dup-ssh-method-doesnt-work- writes-locally-instead -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908791 Title: Backing up to ftp or sftp, creates "sftp:" or "ftp:" folder in Deja- Dup launch place To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/908791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918982] [NEW] gcc 9 compilation fails on atom CPU specifically
Public bug reported: While this may be a bug in gcc, reporting here per https://gcc.gnu.org/bugs/. https://github.com/anarkiwi/atomgccpuzzle based on Ubuntu 20.04, reproduces a difference in behaviour when the gcc frontend runs on an atom-based CPU via qemu (the same issue occurs outside Docker, and/or when run on an Intel Celeron J series CPU). $ docker build -f Dockerfile . [...] ---> Running in cf6eac22eacf Scanning dependencies of target srsenb_mac [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_carrier.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/mac.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/ue.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_grid.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_harq.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_metric.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_ue.cc.o In file included from /root/srsLTE/srsenb/hdr/stack/mac/scheduler_common.h:25, from /root/srsLTE/srsenb/hdr/stack/mac/scheduler_ue.h:25, from /root/srsLTE/srsenb/hdr/stack/mac/scheduler_grid.h:26, from /root/srsLTE/srsenb/src/stack/mac/scheduler_grid.cc:22: /root/srsLTE/lib/include/srslte/adt/bounded_bitset.h: In member function 'srsenb::alloc_outcome_t srsenb::sf_grid_t::alloc_ul_data(srsenb::sched_ue*, srsenb::prb_interval, bool)': /root/srsLTE/lib/include/srslte/adt/bounded_bitset.h:219:32: error: 'newmask.srslte::bounded_bitset<100, true>::buffer[]' may be used uninitialized in this function [-Werror=maybe-uninitialized] 219 | buffer[i] &= other.buffer[i]; |^ cc1plus: all warnings being treated as errors make[3]: *** [srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/build.make:115: srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_grid.cc.o] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [CMakeFiles/Makefile2:8921: srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/all] Error 2 make[1]: *** [CMakeFiles/Makefile2:8928: srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/rule] Error 2 make: *** [Makefile:3265: srsenb_mac] Error 2 The command '/bin/sh -c make -j srsenb_mac' returned a non-zero code: 2 However, a docker build without qemu with the exact same source code, installed packages, base image succeeds. $ docker build -f Dockerfile.ok . [...] ---> Running in e43b65fff3d1 Scanning dependencies of target srsenb_mac [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_grid.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_carrier.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/mac.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/ue.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_harq.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_metric.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler.cc.o [100%] Building CXX object srsenb/src/stack/mac/CMakeFiles/srsenb_mac.dir/scheduler_ue.cc.o [100%] Linking CXX static library libsrsenb_mac.a [100%] Built target srsenb_mac Removing intermediate container e43b65fff3d1 ---> b8f0322dc5f2 Step 14/14 : ENTRYPOINT ["/bin/sh"] ---> Running in 46d14114fafc Removing intermediate container 46d14114fafc ---> 3f781ac8f8bb Successfully built 3f781ac8f8bb $ lsb_release -d Description:Ubuntu 20.04.2 LTS $ gcc -version Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.
[Bug 1915884] Re: Ryzen 5000 Hardware Monitoring Unavailable
I meant to file this against hirsute as a distro. Any way to move this from linux-5.7 (which is the affected package in the distro? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915884 Title: Ryzen 5000 Hardware Monitoring Unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.7/+bug/1915884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915884] [NEW] Ryzen 5000 Hardware Monitoring Unavailable
Public bug reported: Unfortunately support for hardware monitoring slipped to Linux 5.12, which won't land in this version. Missing that in an LTS release will be a disaster of incompatibilities for servers using the newest LTS and silicon. More background - https://www.phoronix.com/scan.php?page=news_item&px=Zen-3-Desktop-CPU- k10temp Zen 3 hardware monitoring can't afford to slip an LTS. Is there anyone here from AMD who might be able to help? ** Affects: linux-5.7 (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/1915884 Title: Ryzen 5000 Hardware Monitoring Unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.7/+bug/1915884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838771] Re: http:Fix Host header in proxied https connections
** Bug watch added: Debian Bug tracker #977930 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930 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/1838771 Title: http:Fix Host header in proxied https connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1838771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907287] [NEW] ansible-playbook imports Python 2.7 jinja2
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 ansible: Installed: 2.9.6+dfsg-1 Candidate: 2.9.6+dfsg-1 Version table: *** 2.9.6+dfsg-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/universe i386 Packages 100 /var/lib/dpkg/status If you install the ansible package, it will install Python 3 as its dependencies. However, the ansible-playbook command imports the Python 2.7 jinja2 module and will fail with the following exception. Traceback (most recent call last): File "/usr/local/bin/ansible-playbook", line 67, in import ansible.constants as C File "/usr/local/lib/python2.7/dist-packages/ansible/constants.py", line 11, in from jinja2 import Template ImportError: No module named jinja2 The workaround is to explicitly install the python-jinja2 package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ansible 2.9.6+dfsg-1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 8 12:21:41 2020 PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ansible UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago) ** Affects: ansible (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/1907287 Title: ansible-playbook imports Python 2.7 jinja2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1907287/+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)
Updating to groovy-proposed libmutter-7-0, mutter, and mutter-common fixed the display issues with the Irfanview (WINE) snap. Woo! -- 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 1853050] Re: Realtek RTL8822BE [10ec:b822] Subsystem [1a3b:2950] Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
This is still an issue for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853050 Title: Realtek RTL8822BE [10ec:b822] Subsystem [1a3b:2950] Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664846] Re: [Wishlist] Support for teaming driver
I'm curious if there has been any movement on this. We switched to using the 'team' driver over the 'bonding' driver some time ago. Having an abstracted network configuration capability through netplan would be very nice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664846 Title: [Wishlist] Support for teaming driver To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1664846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887727] [NEW] Permission denied opening file in a directory with a sticky bit
Public bug reported: We just upgraded to Ubuntu 20.04, so we're now running version 0.8.3-1ubuntu12.1 of zfsutils-linux and related packages. We have a backup server that's essentially rsyncing files from remote systems. After the upgrade we started getting Permission denied failures on a few files, which match a specific pattern: In a directory with a sticky bit set: /zfs# mkdir testdir /zfs# chmod a+t testdir ... which is group writable: /zfs# chmod g+w testdir ... and has an existing file: /zfs# touch testdir/test ... which has a uid which isn't present on the system: /zfs# chown testdir/test ... then an open() call with O_CREAT fails with Permission denied: /zfs# ./openat testdir/test Error opening testdir/test: Permission denied (13) Skip any of those steps and it doesn't throw the error. It's just that specific configuration of directory permissions and file ownership that seems to do it. The ./openat is a simple test case that just runs open() (so named as I was originally testing with the openat() call) and it's attached for reference. We have an rsync --inplace that gets us into that specific scenario. Dropping the --inplace works around it, FWIW, but then we lose a little space within the ZFS snapshots. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Test case" https://bugs.launchpad.net/bugs/1887727/+attachment/5393017/+files/openat.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887727 Title: Permission denied opening file in a directory with a sticky bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
I can also vouch that I run into this issue on a Lenovo Y530-15ICH after upgrading to Focal Fossa. I haven't upgraded my BIOS (I'm afraid to until I'm certain I'm doing it correctly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
This also happens on a Dell XPS 9570. My workaround after reboots, or other events that disable the headphone audio, is to run this: sudo alsactl restore Then things are back to normal for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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.
This is even more important now, with many people working/learning from home... -- 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. 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 1795292] Re: ELAN469D touch pad not working
Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-21-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM [1.387731] kernel: i2c_hid i2c-DELL0926:00: i2c-DELL0926:00 supply vdd not found, using dummy regulator [1.387739] kernel: i2c_hid i2c-DELL0926:00: i2c-DELL0926:00 supply vddl not found, using dummy regulator -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871027] [NEW] xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package
Public bug reported: In xserver-xorg-video-ati the suggested firmware-amd-graphics was dropped because the firmware is part of the linux-firmware package in Ubuntu and since I just ran up on it I thought I would report it so that people are not searching for firmware-amd-graphics for no reason at all. ** Affects: xserver-xorg-video-amdgpu (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/1871027 Title: xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1871027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-21-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8797] NetworkManager (version 1.22.10) is starting... (for the first time) Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8798] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-po> Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8798] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 02 17:53:55 buntu NetworkManager[737]: [1585868035.8798] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-21-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Apr 02 17:53:55 buntu kernel: platform eisa.0: Probing EISA bus 0 Apr 02 17:53:55 buntu kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Apr 02 17:53:55 buntu kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 Apr 02 17:53:55 buntu kernel: platform eisa.0: EISA: Detected 0 cards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-18-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Dell Precision 7540 Ubuntu Certified Machine came with Ubuntu 18.03 Acpi dump is comment #22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806437] Re: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
** Attachment added: "acpi-dump.bin" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806437/+attachment/5341270/+files/acpi-dump.bin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862548] [NEW] jdkhome flag doesn't work
Public bug reported: Trying to use --jdkhome flag with the default visualvm (1.4.2 190225) with openjdk-8-jdk (8u242-b08-0ubuntu3~18.04) doesn't work. The command I am running is $ visualvm --jdkhome /usr/lib/jvm/java-1.8.0-openjdk-amd64 The splash will appear and then the program will close with no message, error or otherwise. However running the same command with the copy of visualvm downloaded from https://visualvm.github.io (at the time of writing 1.4.4 build 190918) the command works successfully. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: visualvm 1.4.2-2~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: i3 Date: Mon Feb 10 10:57:53 2020 InstallationDate: Installed on 2019-07-12 (212 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: visualvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: visualvm (Ubuntu) Importance: Undecided Status: New ** Tags: openjdk-8-jdk visualvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862548 Title: jdkhome flag doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/visualvm/+bug/1862548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
Unfortunately upon investigation of the fix Andrés mentioned in #18, I found that my system (Eoan, 5.3.0-24, Lenovo W540) was already configured for deep and not s2idle and is still affected by the 'gpu has fallen off the bus' issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857176] [NEW] [PLT V8200 Series, playback] Playback problem
Public bug reported: Hi, what happened was - I changed my input device to this device and when I did I noticed the output (to same device) became degraded. I was able to fix by setting it from high fidelity, back to headset, and back to high fidelity again. So, it seems setting the input device did some sort of 'configuration reset' that was not shown in the UI. Thanks! Wonderful OS :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jdix 1978 F pulseaudio /dev/snd/controlC0: jdix 1978 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 20 16:52:06 2019 InstallationDate: Installed on 2018-10-08 (438 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: PLT V8200 Series Symptom_Type: None of the above Title: [PLT V8200 Series, playback] Playback problem UpgradeStatus: Upgraded to eoan on 2019-10-31 (50 days ago) dmi.bios.date: 06/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L3.24 dmi.board.name: X470 Master SLI/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL3.24:bd06/04/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470MasterSLI/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857176 Title: [PLT V8200 Series, playback] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853609] [NEW] jpnevulator uses 100% cpu after resume
Public bug reported: If jpnevulator is left running while the system is suspended, it begins to consume 100% of CPU time on one core upon resume. The specific command line I'm using is: jpnevulator -r -a --tty /dev/ttyACM0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: jpnevulator 2.3.4-1 ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18 Uname: Linux 4.15.0-69-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: i3 Date: Fri Nov 22 14:29:05 2019 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 InstallationDate: Installed on 2018-08-13 (465 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: jpnevulator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jpnevulator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - If jpnevaluator is left running while the system is suspended, it begins + If jpnevulator is left running while the system is suspended, it begins to consume 100% of CPU time on one core upon resume. The specific command line I'm using is: - jpnevulator -r -a --tty /dev/ttyACM0 + jpnevulator -r -a --tty /dev/ttyACM0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: jpnevulator 2.3.4-1 ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18 Uname: Linux 4.15.0-69-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: i3 Date: Fri Nov 22 14:29:05 2019 Dependencies: - gcc-8-base 8.3.0-6ubuntu1~18.04.1 - libc6 2.27-3ubuntu1 - libgcc1 1:8.3.0-6ubuntu1~18.04.1 + gcc-8-base 8.3.0-6ubuntu1~18.04.1 + libc6 2.27-3ubuntu1 + libgcc1 1:8.3.0-6ubuntu1~18.04.1 InstallationDate: Installed on 2018-08-13 (465 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: jpnevulator 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/1853609 Title: jpnevulator uses 100% cpu after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jpnevulator/+bug/1853609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851997] [NEW] Typo in im-launch(1) man page
Public bug reported: im-launch(1) says: im-launch - launch input method end execute session program but should say: im-launch - launch input method and execute session program (s/end/and/) This is an upstream bug[1] which should be reported to Debian, but frankly I'm not up to dealing with the Debian BTS at the moment. [1]: https://salsa.debian.org/input-method-team/im- config/blob/24779d612f14c5f6c32ae789c7e7091fd859e7ec/im-launch.1#L5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: im-config 0.34-1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: i3 Date: Sun Nov 10 15:04:15 2019 InstallationDate: Installed on 2018-08-13 (453 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: im-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851997 Title: Typo in im-launch(1) man page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1851997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839533] [NEW] .whl/.egg support in lesspipe is undocumented
Public bug reported: Support for .whl/.egg files (used in Python packaging) was added to lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page was apparently not updated at the time, and does not currenly list .whl/.egg as supported file types. This looks like a Debian bug, since the manual page was apparently written for Debian, but reportbug complains at me when I try to use it to submit a bug to the Debian BTS, so hopefully someone who knows what they're doing can report this upstream. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862048 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: i3 Date: Thu Aug 8 20:07:51 2019 Dependencies: debianutils 4.8.4 gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (360 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: less (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839533 Title: .whl/.egg support in lesspipe is undocumented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1839533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837959] [NEW] no syntax highlighting for java
Public bug reported: Installed a fresh copy of eclipse, but on opening a java file no syntax highlighting. In addition no mention of the SDK in the create new project nor of anything Java related in 'File Associations'. I also can't seem to access the internal editor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eclipse 3.8.1-11 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 26 14:14:21 2019 InstallationDate: Installed on 2019-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eclipse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1837959 Title: no syntax highlighting for java To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1837959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
Ah, sorry. I swapped this card for an Intel one years ago. I had never tried the Realtek card on windows either. Thanks anyway for following up, - Josh On Thu, Jul 25, 2019 at 8:34 AM Larry Finger wrote: > I reached my contact at Realtek. He analyzed the output and thinks that > this particular chip has a faulty EFUSE programming, or that it possible > was not programmed in the factory. Either case should have been caught > in testing, but mistakes happen. > > Has this card been tested on Windows 10? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1239578 > > Title: > No wireless support for Realtek RTL8192EE [10ec:818b] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions > -- :wq -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125]
Hi all, I have been following this bug report for a while - I just wanted to check in on status. Will the fix be rolled out now that Paulo has confirmed the working kernel version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832153] [NEW] game-data-packager fails to download wolf3d data
Public bug reported: As reported upstream at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=911788, game-data-packager version 58 attempts to download data for Wolfenstein 3D from http://pkg-games.alioth.debian.org /game-data/1wolf14.zip, which is no longer available since Alioth was shut down. This is (presumably) a regression, since when Ubuntu 18.04 was released, Alioth was still online. $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy game-data-packager game-data-packager: Installed: 58 Candidate: 58 Version table: *** 58 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: game-data-packager 58 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: i3 Date: Mon Jun 10 03:23:57 2019 InstallationDate: Installed on 2018-08-13 (300 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: game-data-packager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: game-data-packager (Ubuntu) Importance: Undecided Status: New ** Affects: game-data-packager (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug bionic ** Bug watch added: Debian Bug tracker #911788 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911788 ** Also affects: game-data-packager (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911788 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/1832153 Title: game-data-packager fails to download wolf3d data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/game-data-packager/+bug/1832153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
For anyone experiencing this issue with a Realtek RTL8411 card reader: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) Subsystem: CLEVO/KAPOK Computer RTL8411B PCI Express Card Reader Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at a4215000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at a420 [disabled] [size=64K] Capabilities: Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci the out-of-tree rts_bpp module appears to work fine with kernel version 4.15.0-47: https://github.com/Ri0n/rts_bpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
Same issue here, also with a SanDisk Extreme microSD card (128GB). Possibly relevant: https://bugzilla.kernel.org/show_bug.cgi?id=202473 ** Bug watch added: Linux Kernel Bug Tracker #202473 https://bugzilla.kernel.org/show_bug.cgi?id=202473 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
Comment #19 PPA solved issue for me, will notify if it remains solved after a few reboots. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822838] Re: [regression][nvidia] gnome-shell is very large
Bug returns after 2 reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822838 Title: [regression][nvidia] gnome-shell is very large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734243] Re: Intel 9260/9462/9560 firmware support
6b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) This was never really fixed for the 9260 on 5ghz. Rarely connects at 5ghz and very slow. I've tried the most recent linux kernel and the most recent ubuntu kernel. BT and 2.4ghz is fine. :6b:00.0: Unhandled alg: 0x707 Reverted to 4.18.0-17-generic and same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734243 Title: Intel 9260/9462/9560 firmware support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822838] Re: [regression][nvidia] gnome-shell is very large
Bug has returned, not sure why to be honest but it seems like this should be fixed, I saw other people having trouble with this as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822838 Title: [regression][nvidia] gnome-shell is very large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822838] Re: [nvidia] gnome-shell is very large
This worked like a charm. Thanks Daniel!! Issue has been resolved. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1822838 Title: [nvidia] gnome-shell is very large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822838] Re: [nvidia] gnome-shell is very large
Bug still persists on those versions, installed all the .deb packages with Package Manager, didn't work unfortunately. My OS froze and had to fix with command line. Maybe I did something wrong, but it didn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822838 Title: [nvidia] gnome-shell is very large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822858] Re: In Ubuntu desktop, alt-tab twice does not return you to same window
** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822858 Title: In Ubuntu desktop, alt-tab twice does not return you to same window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822838] [NEW] gnome-shell is very large
Public bug reported: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. Notifications, etc are extremely large. Just everything from the shell is like 40% larger than it should be. This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Everything from gnome-shell is very large. I use NVIDIA drivers. Tried reinstalling gnome-shell, disabled extensions, checked scaling, deleted setting files, nothing worked. I created a new user, gnome-shell has the same issue in the beginning. Alt + F2 resets shell to normal size, but on logout/login everything is large again. This doesn't work on my user tho. - Notifications, etc are extremely large. + Notifications, etc are extremely large. - Just everything from the shell is like 40% larger as it should be. This - also happens with default themes, settings, etc. + Just everything from the shell is like 40% larger than it should be. + This also happens with default themes, settings, etc. Screenshot: https://imgur.com/a/oo5I7lZ gnome-shell: 3.32.0 OS: Ubuntu 19.04 Development Branch ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:14:00 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-09 (82 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-30 (3 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822838 Title: gnome-shell is very large To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821660] [NEW] package libbdplus0:amd64 0.1.2-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Attempted to install to allow folder sharing. Install failed. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libbdplus0:amd64 0.1.2-3 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Mon Mar 25 22:29:37 2019 DuplicateSignature: package:libbdplus0:amd64:0.1.2-3 Processing triggers for gnome-menus (3.13.3-11ubuntu2) ... dpkg: error processing package libbdplus0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-03-24 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: libbdplus Title: package libbdplus0:amd64 0.1.2-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libbdplus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821660 Title: package libbdplus0:amd64 0.1.2-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbdplus/+bug/1821660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304067] Re: Mouse cursor changes size in some GTK2 applications
#26 solution is the only one that worked for me. NUC7i7BNH on Juno (Ubuntu 18.04.2 LTS) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304067 Title: Mouse cursor changes size in some GTK2 applications To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1304067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815329] [NEW] package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'hal
Public bug reported: Just updated and received critical errors. not sure whats wrong. also having trouble printing... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: python3-smbc: Install libkpathsea6: Configure python3-smbc: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Feb 9 21:23:11 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-02-09 21:23:10 Commandline: aptdaemon role='role-install-packages' sender=':1.106' Install: python3-smbc:amd64 (1.0.15.5-1) DuplicateSignature: package:libkpathsea6:amd64:2015.20160222.37495-1ubuntu0.1 Unpacking python3-smbc (1.0.15.5-1) ... dpkg: error processing package libkpathsea6:amd64 (--configure): package libkpathsea6:amd64 is not ready for configuration ErrorMessage: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-12-28 (408 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: texlive-bin Title: package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-bin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815329 Title: package libkpathsea6:amd64 2015.20160222.37495-1ubuntu0.1 failed to install/upgrade: package libkpathsea6:amd64 is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1815329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813400] [NEW] systemctl doesn't respect --dry-run
Public bug reported: [Expected behaviour] When I use the --dry-run flag with systemctl, I would expect it not to take any action, but instead print what it is going to do. [Actual behaviour] Passing --dry-run doesn't affect the behaviour of systemctl. [Test case] $ systemctl --dry-run reboot Ubuntu version: 18.04.1 systemd version: 237-3ubuntu10.11 ** Affects: systemd (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/1813400 Title: systemctl doesn't respect --dry-run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using i3wm
Ok, thanks; I guess I'll live with the tearing for now, then. I agree that it seems a bit pointless/unlikely to spend time fixing this given most people won't run into it now that compositors are so common. Maybe I'll get around to configuring one at some point :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using i3wm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
> Does using a Wayland session avoid the bug? Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note: after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 && apt autoremove --purge`), I have to boot with `nouveau.modeset=0`, otherwise boot hangs at Plymouth after entering my disk encryption password.) In Wayland, xrandr prints the following: $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 340mm x 190mm 1920x1080 59.96*+ > Also, what shell are you using? If you mean shell-as-in-graphical, and I understand correctly what that means, then I'm using i3wm. If you mean shell-as-in-CLI, then bash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Tearing in Totem with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230257/+files/totem-tearing.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
I'm using only one monitor (the one built-in to the laptop), at times I use an external monitor as well, but this problem persists without it plugged in. After removing that block (i.e. using the modesetting driver), I get jagged tearing almost everywhere. Both Chrome and Totem tear very noticeably, but in slightly different ways (I'll attach some pictures). However, when Chrome is in fullscreen mode, there's no tearing at all, but Totem continues to tear when fullscreened. ** Attachment added: "Tearing in Chrome with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230256/+files/chrome-tearing.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230058/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
This Xorg.1.log was last modified in November, so I'm unsure if it's relevant. ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230059/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
I don't have an /etc/X11/xorg.conf, but I do have (along with the various distribution-provided files) a /usr/share/X11/xorg.conf.d/99-custom.conf. ** Attachment added: "99-custom.conf" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230057/+files/99-custom.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
Unfortunately, the BIOS doesn't have an option to disable the Nvidia GPU. ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230056/+files/allpackages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
@Alberto: would you be open to adding it again? I need to enable TearFree and select the Intel driver when using my integrated GPU (but if I have `Driver "intel"` in my config when using the Nvidia GPU, I get a black screen on login), so it would be nice to have a way to automatically put a file in xorg.conf.d when switching the GPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Output of `vainfo`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Output of `lscpu`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
Removing gstreamer1.0-vaapi doesn't appear to help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics
** Attachment added: "Output of `lspci -k`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811808] [NEW] Tearing and/or flickering when using Intel graphics
Public bug reported: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if I enable TearFree (which eliminates tearing in Chrome), the tearing turns into jagged black flickers which extend from the top of the screen right down to near the bottom of the screen on some frames. The flickers are visible in screenshots, so I have attached one. Ubuntu version: Ubuntu 18.04.1 Totem version: 3.26.0-0ubuntu6.1 ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Attachment added: "flickering with TearFree enabled" https://bugs.launchpad.net/bugs/1811808/+attachment/5229271/+files/Screenshot%20from%202019-01-03%2016-49-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
This is no longer found in Bionic, since ubuntu-drivers-common 1:0.5 (see [1]). Was this feature intentionally removed? [1]: https://git.launchpad.net/ubuntu/+source/ubuntu-drivers- common/commit/share/hybrid/gpu- manager.c?id=fb450c8eddf9290225e198ce92123e4fff346589 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
