[Bug 1904884] Re: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click
Same problem mouse is Steeleries Rival 110 My configuration is p-i@pi-TUF-Gaming-B550M:~$ inxi -Fz System:Kernel: 5.8.0-25-generic x86_64 bits: 64 Desktop: GNOME 3.38.1 Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x serial: UEFI: American Megatrends v: 1212 date: 11/04/2020 CPU: Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 2196 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 2198 2: 2198 3: 2199 4: 2200 5: 2199 6: 2194 7: 2198 8: 2201 9: 2193 10: 2195 11: 2194 12: 2192 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1440~60Hz OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.38.0 5.8.0-25-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.2 Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.8.0-25-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi IF: wlp6s0 state: up mac: Device-2: Realtek RTL8125 2.5GbE driver: N/A Drives:Local Storage: total: 1.36 TiB used: 24.03 GiB (1.7%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 GiB ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB Partition: ID-1: / size: 456.96 GiB used: 24.00 GiB (5.3%) fs: ext4 dev: /dev/sda2 Swap: ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: /swapfile Sensors: System Temperatures: cpu: 0.0 C mobo: N/A gpu: amdgpu temp: 46.0 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 Info: Processes: 362 Uptime: 2m Memory: 15.54 GiB used: 2.20 GiB (14.2%) Shell: Bash inxi: 3.1.09 p-i@pi-TUF-Gaming-B550M:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905946 Title: Mouse stop moving after few seconds. restart at click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906097] [NEW] can not do a release upgrade from 18.04 to 20.04
Public bug reported: when runnuning do-release-upgrade -d -f DistUpgradeViewGtk3 upgrade installation fails 1) lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 2) do-release-upgrade -d -f DistUpgradeViewGtk3 3) I expect getting upgraded from Ubuntu 18.04 to 20.04 4) Distribution upgrade fails: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was caused by: * Upgrading to a pre-release version of Ubuntu This is most likely a transient problem, please try again later. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu Date: Sat Nov 28 08:33:13 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-28 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906097 Title: can not do a release upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1906097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906095] [NEW] Fails to boot
Public bug reported: 1) Ubuntu 20.10 2) kernel 5.8.0-29-generic 3) To boot 4) Instead the boot screen only shows up on one monitor and freezes ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-29-generic 5.8.0-29.31 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Nov 28 00:21:51 2020 InstallationDate: Installed on 2020-11-19 (8 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=b19340a3-b1fa-4e95-88ea-3b3d2ff8e4f6 ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3201 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X299-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3201:bd09/04/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX299-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906095 Title: Fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906096] [NEW] Pressing Shift + 9 should give opening parentheses and Pressing Shift + 0 should give closing parentheses.
Public bug reported: That's how it should respond. That's how it respond in Windows and other OS. Pressing Shift + 1 gives ! Pressing Shift + 2 gives @ ... and so on. Everything works fine until when we reach the 9 and 0 key. Pressing Shift + 9, it gives 9 instead of ( and Pressing Shift + 0, it gives 0 instead of ) This is a globally recognized "keyboard pattern". This fails if u select Nepali Keyboard. I don't know why. It makes things harder for us to write opening and closing parenthesis unless we use Windows OS. Please fix this. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: language-pack-gnome-ne 1:20.10+20201015 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 13:02:24 2020 InstallationDate: Installed on 2020-02-16 (285 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: language-pack-gnome-ne UpgradeStatus: Upgraded to groovy on 2020-10-28 (30 days ago) ** Affects: language-pack-gnome-ne (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "What a Nepali Keyboard look like!" https://bugs.launchpad.net/bugs/1906096/+attachment/5438981/+files/Screenshot%20from%202020-11-21%2010-02-18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906096 Title: Pressing Shift + 9 should give opening parentheses and Pressing Shift + 0 should give closing parentheses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-ne/+bug/1906096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906092] Re: Echoping segfaults when installing smokeping
Sorry, not core files. Crash file, contents as follows: Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: echoping 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 63.4 kB of archives. After this operation, 251 kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 echoping amd64 6.0.2-10ubuntu1 [63.4 kB] Fetched 63.4 kB in 1s (62.0 kB/s) Selecting previously unselected package echoping. (Reading database ... 122202 files and directories currently installed.) Preparing to unpack .../echoping_6.0.2-10ubuntu1_amd64.deb ... Unpacking echoping (6.0.2-10ubuntu1) ... Setting up echoping (6.0.2-10ubuntu1) ... Processing triggers for man-db (2.9.1-1) ... root@linux-mgmt:/# cd /var/log root@linux-mgmt:/var/log# ls alternatives.logapport.log auth.log.1 chrony dist-upgrade dpkg.loggrafana kern.log.1 lost+found syslog.1 wtmp alternatives.log.1 apt btmpcloud-init-output.log dmesg dpkg.log.1 influxdb landscape private telegraf apache2 auth.logbtmp.1 cloud-init.log dmesg.0 fontconfig.log kern.log lastlog syslog unattended-upgrades root@linux-mgmt:/var/log# tail -f kern.log Nov 27 23:06:02 linux-mgmt kernel: [ 2463.644955] echoping[8246]: segfault at 1f51f5e0 ip 7f6d586b25e9 sp 7fffaf6ca810 error 4 in dns.so.0.0.0[7f6d586b2000+1000] Nov 27 23:06:02 linux-mgmt kernel: [ 2463.644971] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:06:02 linux-mgmt kernel: [ 2463.654566] echoping[8249]: segfault at 4b14b5e0 ip 7f2043d955e9 sp 7c3c01c0 error 4 in dns.so.0.0.0[7f2043d95000+1000] Nov 27 23:06:02 linux-mgmt kernel: [ 2463.654581] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:06:02 linux-mgmt kernel: [ 2463.656033] echoping[8244]: segfault at acfbd5e0 ip 7f30b2a255e9 sp 7ffda4b873f0 error 5 in dns.so.0.0.0[7f30b2a25000+1000] Nov 27 23:06:02 linux-mgmt kernel: [ 2463.656042] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:06:02 linux-mgmt kernel: [ 2463.707126] echoping[8248]: segfault at 741785e0 ip 7f94a97f35e9 sp 7ffcd473e550 error 4 in dns.so.0.0.0[7f94a97f3000+1000] Nov 27 23:06:02 linux-mgmt kernel: [ 2463.707141] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:06:02 linux-mgmt kernel: [ 2463.708512] echoping[8251]: segfault at 3085c5e0 ip 7f39a51965e9 sp 7ffe01008ed0 error 4 in dns.so.0.0.0[7f39a5196000+1000] Nov 27 23:06:02 linux-mgmt kernel: [ 2463.708521] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://us.archive.ubuntu.com/ubuntu focal main restricted # deb-src http://us.archive.ubuntu.com/ubuntu focal main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://us.archive.ubuntu.com/ubuntu focal-updates main restricted # deb-src http://us.archive.ubuntu.com/ubuntu focal-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://us.archive.ubuntu.com/ubuntu focal universe # deb-src http://us.archive.ubuntu.com/ubuntu focal universe deb http://us.archive.ubuntu.com/ubuntu focal-updates universe # deb-src http://us.archive.ubuntu.com/ubuntu focal-updates universe "sources.list" 49L, 2777C 1,1 Top ^C root@linux-mgmt:/var/log# apt-get source echoping Reading package lists... Done E: You must put some 'deb-src' URIs in your sources.list root@linux-mgmt:/var/log# vi /etc/apt/sources.list sources.list sources.list.curtin.old sources.list.d/ sources.list.save root@linux-mgmt:/var/log# vi /etc/apt/sources.list.d/ ansible-ubuntu-ansible-focal.list grafana.list grafana.list.save influxdb.list influxdb.list.save root@linux-mgmt:/var/log# cd
[Bug 1906092] [NEW] Echoping segfaults when installing smokeping
Public bug reported: Running: PRETTY_NAME="Ubuntu 20.04.1 LTS" VERSION_ID="20.04" Installed smokeping: sudo apt install smokeping Noticed core files under /var/crash: -rw-r- 1 smokeping smokeping 177182 Nov 27 23:14 _usr_bin_echoping.117.crash And many segmentation fault errors in kern.log: Nov 27 23:16:02 linux-mgmt kernel: [ 3063.653421] echoping[8532]: segfault at 407295e0 ip 7f273b02e5e9 sp 7ffeb61433c0 error 4 in dns.so.0.0.0[7f273b02e000+1000] Nov 27 23:16:02 linux-mgmt kernel: [ 3063.653433] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:16:02 linux-mgmt kernel: [ 3063.657597] echoping[8534]: segfault at e526e5e0 ip 7fc81b5875e9 sp 7ffc106b1220 error 5 in dns.so.0.0.0[7fc81b587000+1000] Nov 27 23:16:02 linux-mgmt kernel: [ 3063.657612] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:16:02 linux-mgmt kernel: [ 3063.686165] echoping[8536]: segfault at 7eb745e0 ip 7fabc03945e9 sp 7ffcb6dedf20 error 4 in dns.so.0.0.0[7fabc0394000+1000] Nov 27 23:16:02 linux-mgmt kernel: [ 3063.686180] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Nov 27 23:16:02 linux-mgmt kernel: [ 3063.688608] echoping[8538]: segfault at 56695e0 ip 7f98013bf5e9 sp 7ffdfa5c7430 error 4 in dns.so.0.0.0[7f98013bf000+1000] Nov 27 23:16:02 linux-mgmt kernel: [ 3063.688635] Code: 08 01 00 00 5b 5d 41 5c 41 5d c3 66 0f 1f 44 00 00 31 c0 e8 99 fb ff ff b9 02 00 00 00 48 8d 3d c6 0a 00 00 48 63 d8 48 89 de a6 0f 97 c0 1c 00 84 c0 74 7c b9 05 00 00 00 48 8d 3d a6 0a 00 Did some research and it seems this issue is related with echoping using instructions that are not working under amd64 architecture. A previous workaround was to install the i386 version of the package which is not possible anymore. Reference: http://unix.stackexchange.com/questions/513895/ddg#513913 ** Affects: echoping (Ubuntu) Importance: Undecided Status: New ** Affects: unscd (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/1906092 Title: Echoping segfaults when installing smokeping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/echoping/+bug/1906092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
Adding dis_ucode_ldr to boot options fixed it for me (https://www.dell.com/community/Precision-Mobile- Workstations/Precision-7540-will-only-boot-Linux-if-charger-is- connected/m-p/7466713/highlight/true#M2874). Million kiddos for flea plus, the original poster. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1905947 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905947 Title: lubuntu hirsute: display configuration doesn't survive logout/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906091] [NEW] libx264-148 libx264-152 conflict segmentation fault SIGSEGV
Public bug reported:
In my app I have segfault due to conflict of libx264-148 vs libx264-152.
I use gstreamer and libopencv_videoio in my project.
System is Ubuntu 18.04.5
The problem is that versions of libx264 get mixed due to implicit
linking.
Libraries are linked like this:
gstreamer -> x264enc -> libx264-152
libopencv_videoio -> libavcodec-ffmpeg.so.56 -> libx264-148
Both opencv-based code and gstreamer-based code works well if used
separately.
At the top of backtrace I see:
Thread 13 (Thread 0x7f28e2066700 (LWP 26012)):
#0 0x7f290181c853 in x264_add8x8_idct_avx2.skip_prologue () at
/usr/lib/x86_64-linux-gnu/libx264.so.152 // 152
#1 0x7f2927a93f55 in x264_nal_encode () at
/usr/lib/x86_64-linux-gnu/libx264.so.148 // 148
#2 0x7f2927af866c in () at /usr/lib/x86_64-linux-gnu/libx264.so.148
#3 0x7f2927b0143b in x264_encoder_headers () at
/usr/lib/x86_64-linux-gnu/libx264.so.148
If I use objdump I can find x264_add8x8_idct_avx2.skip_prologue in both
libx264-148 and libx264-152
Here is example code which fails (C++ needed):
int main (int argc, char *argv[])
{
App *app = _app;
GError *error = NULL;
GstBus *bus;
GstCaps *caps;
gst_init (, );
auto cap = cv::VideoCapture("videoplayback.mp4");
cv::Mat f;
cap.read(f);
cv::imshow("f", f);
GST_DEBUG_CATEGORY_INIT (appsrc_pipeline_debug, "appsrc-pipeline", 0,
"appsrc pipeline example");
app->loop = g_main_loop_new (NULL, TRUE);
app->timer = g_timer_new();
app->pipeline = gst_parse_launch(R"(filesrc location=videoplayback.mp4
! decodebin ! videoconvert ! x264enc byte-stream=true
threads=1 tune=zerolatency
bitrate=400 key-int-max=50 option-
string="force-cfr=1" ! video/x-h264,profile=baseline,stream-
format="byte-stream" ! h264parse ! mpegtsmux !
hlssink location="/tmp/data%06d.ts" max-
files=100 playlist-length=10 playlist-
location="/tmp/kek" target-duration=10
playlist-root=".")", NULL);
g_assert (app->pipeline);
bus = gst_pipeline_get_bus (GST_PIPELINE (app->pipeline));
g_assert(bus);
gst_bus_add_watch (bus, (GstBusFunc) bus_message, app);
caps = gst_caps_new_simple ("video/x-raw-rgb",
"bpp",G_TYPE_INT,8,
"depth",G_TYPE_INT,8,
"width", G_TYPE_INT, 640,
"height", G_TYPE_INT, 480,
NULL);
gst_element_set_state (app->pipeline, GST_STATE_PLAYING);
g_main_loop_run (app->loop);
GST_DEBUG ("stopping");
gst_element_set_state (app->pipeline, GST_STATE_NULL);
gst_object_unref (bus);
g_main_loop_unref (app->loop);
return 0;
}
How can I solve this? PLease help!
** Affects: x264 (Ubuntu)
Importance: Undecided
Status: New
** Tags: gst gstreamer h264 libx264 opencv
** Summary changed:
- libx264-148 libx264-152 conflict segmentation failt SIGSEGV
+ libx264-148 libx264-152 conflict segmentation fault SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906091
Title:
libx264-148 libx264-152 conflict segmentation fault SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1906091/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot
Lubuntu hirsute daily QA-test on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) this box shares displays with prior comment (d755-8) so landscape+portrait, though opposite order due cables saved & applied monitor.settings logout & login again. Monitor.settings did NOT survive logout & login here... On same box I booted Lubuntu focal daily (yesterdays) repeating the same identical test. Differences here are only the left-right appear differently, so I swap left+right, then right is made portrait-left. On focal daily, the monitor.settings survive logout in the live session, as they instantly appear on login again. ** Description changed: - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) + - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) + + dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) + + dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) ** background QA-test install, login to a ~recent hirsute install (untouched) to verify nothing has changed, screens aren't in correct orientation?? yet command history from my validation post-install is present (I always adjust displays post-install as part of confirmation install is good). No problem, I'll adjust monitor settings again, logout and log back in as a test (I've noted this behavior before recently, but just ignored it as it gets erased next qa-test) - ** issue & re-creation steps - adjust displays to match setup. My displays are one above the other. The default-right monitor gets moved to above-the-other. APPLY and SAVE settings. - logout - login again ** expected result I expect the screens return to the setup I applied & saved ** actual result Monitor settings have returned to the original left-right as they were before changing setting, or post install. Same occurs after a reboot + + ** another test strategy + + - using a Lubuntu live system, boot & adjust monitor.settings + - logout + - login again + + On focal daily (20.04.2) the changed settings survive logout/login, on + current hirsute they do not; just as installed systems. ** more notes this could be related to the above-below orientation of a number of my boxes; so won't be experienced by many users. My guess I've been noting this for about a week (very subjective), including on my primary box (maybe 3 logins; it's not occurring on suspends which I use most nights). On my primary box, I experienced a crashed session (forced logout) and was willing to blame it as a consequence of the crashed session; this is a pristine install. (I believe i've seen it on landscape+portrait, but I'll have to confirm that via re-test, (either one of d780 or d755-8, but as I couldn't re- create on other box I ignored it. I've filed now as this is now 3 sets- of-displays involved meaning at least 3 boxes; each of my displays are used by multiple boxes) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lxqt-config 0.15.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Fri Nov 27 18:05:57 2020 InstallationDate: Installed on 2020-11-20 (7 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201119) SourcePackage: lxqt-config 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/1905947 Title: lubuntu hirsute: display configuration doesn't survive logout/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot
Lubuntu hirsute daily QA-test install on - dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) testcase: install alongside .. reboot, login to new system, .. adjust displays to match my setup .. on logout, I logged back in and displays returned to default (as it was on first login), not my applied/saved changes.. so https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947 this box uses landscape+portrait displays, so different monitor.setup to the dc7700 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905947 Title: lubuntu hirsute: display configuration doesn't survive logout/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1905947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906088] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906088 Title: Touchpad is not detected and not responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890435] Re: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault
To be sure i was running r10-7093 again and so far got 8 good runs in a row :-/ If only we could have a better trigger :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890435 Title: gcc-10 breaks on armhf (flaky): internal compiler error: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/groovy/+bug/1890435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905228] Re: DIsplay Rotates to Portrait Mode when Certain Apps Open
The bug doesn't occur in Xorg and the Auto-rotate overall is much faster and more responsive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905228 Title: DIsplay Rotates to Portrait Mode when Certain Apps Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906088] [NEW] Touchpad is not detected and not responsive
Public bug reported: 1. See attachment 2. Vendor is Microsoft ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: niteshb1201 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 11:00:25 2020 InstallationDate: Installed on 2020-11-28 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=c57708b6-f80b-474d-92fa-b586f01e6b4c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN40WW:bd08/10/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1906088/+attachment/5438939/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906088 Title: Touchpad is not detected and not responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906087] [NEW] Half of the date-time font is hidden when using Language Tamil-india
Public bug reported: I am using Tamil(india) as the date-time language from Ubuntu 19. But after upgrading to Ubuntu 20, the date-time is half-hidden (see attachments). before upgrade it was working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 10:47:42 2020 DistUpgraded: 2020-06-06 18:27:37,926 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0792] InstallationDate: Installed on 2018-11-04 (755 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=6272611c-ab7e-4b80-86ed-8e7dbe8d5396 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-06 (174 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 0T1X3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal fonts ubuntu ** Attachment added: "Shows the how the font is hidden" https://bugs.launchpad.net/bugs/1906087/+attachment/5438919/+files/Screenshot%20from%202020-11-28%2010-58-11.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906087 Title: Half of the date-time font is hidden when using Language Tamil-india To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893538] Re: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04
This is being fixed in 1905214. I've tested the focal-proposed package already and it appears to work fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893538 Title: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1893538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905768] Re: ld: DWARF error: could not find variable specification at offset
** Changed in: binutils (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905768 Title: ld: DWARF error: could not find variable specification at offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1905768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
Kernel in proposed solved the problem, system can now boot correctly with monitor connected on WD19 docking, with docking connected on system TBT port. Done 10 cold boot and 10 warm boot cycles, all pass. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903969 Title: failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524339] Re: virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524339 Title: virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1524339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524339] Re: virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount
[Expired for Ubuntu Cloud Archive because there has been no activity for 60 days.] ** Changed in: cloud-archive Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524339 Title: virsh failure to start lxc container - internal error: Unable to find 'cpuacct' cgroups controller mount To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1524339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897206] Re: package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: mount: /var/lib/grub/esp: special device /, does not exist.
[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shim-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897206 Title: package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: mount: /var/lib/grub/esp: special device /, does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1897206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897521] Re: Installer crashes during/after the dpkg step
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897521 Title: Installer crashes during/after the dpkg step To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] Re: gedit needs classic confinement
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897562 Title: gedit needs classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906086] [NEW] DIsplay is limited to top half of the screen
Public bug reported: Display is limited to the top half of the screen. I have tried changing the resolution, without success. I am attempting to trial Ubuntu 20.10 from a USB stick. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.445.1 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 04:09:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8058] LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteOne 800 G2 23-in Touch AiO ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.vendor: HP dmi.bios.version: N11 Ver. 02.45 dmi.board.name: 8058 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.asset.tag: AUD6100LCF dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN11Ver.02.45:bd12/24/2019:svnHP:pnHPEliteOne800G223-inTouchAiO:pvr:rvnHP:rn8058:rvrKBCVersion05.39:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteOne 800 G2 23-in Touch AiO dmi.product.sku: T6T88PA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906086 Title: DIsplay is limited to top half of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1906086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906079] Re: Both ethernet and wifi not working after upgrade from ubuntu 18 to 20
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906079 Title: Both ethernet and wifi not working after upgrade from ubuntu 18 to 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1906079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906081] Re: grub failed to update on reinstall from 20.10 media, 20.04 installs without issue.
** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906081 Title: grub failed to update on reinstall from 20.10 media, 20.04 installs without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1906081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906084] [NEW] Ubuntu 20.04 desktop installation crashes
Public bug reported:
I choose manual modification for disk partitions ("Something else" button) and
got installation crash.
Root (/) - on /dev/sda2, Var (/var) - on lvm.
Last messages from /var/log/syslog:
Nov 28 03:56:02 ubuntu ubiquity[6069]: Reverting lockdown of the desktop
environment.
Nov 28 03:56:04 ubuntu /install.py: Exception during installation:
Nov 28 03:56:04 ubuntu /install.py: Traceback (most recent call last):
Nov 28 03:56:04 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 764, in
Nov 28 03:56:04 ubuntu /install.py: install.run()
Nov 28 03:56:04 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 135, in run
Nov 28 03:56:04 ubuntu /install.py: self.copy_all()
Nov 28 03:56:04 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 512, in copy_all
Nov 28 03:56:04 ubuntu /install.py: self.db.progress('SET', 10 +
copy_progress)
Nov 28 03:56:04 ubuntu /install.py: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Nov 28 03:56:04 ubuntu /install.py: lambda *args, **kw:
self.command(command, *args, **kw))
Nov 28 03:56:04 ubuntu /install.py: File
"/usr/lib/python3/dist-packages/debconf.py", line 88, in command
Nov 28 03:56:04 ubuntu /install.py: self.write.flush()
Nov 28 03:56:04 ubuntu /install.py: BrokenPipeError: [Errno 32] Broken pipe
Nov 28 03:56:04 ubuntu /install.py:
Ubuntu version:
# lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
Date: Sat Nov 28 08:54:50 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 focal ubiquity-20.04.15.2 ubuntu
** Attachment added: "/var/log/syslog and /var/log/partman are in this file"
https://bugs.launchpad.net/bugs/1906084/+attachment/5438893/+files/log.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906084
Title:
Ubuntu 20.04 desktop installation crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1906084/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906067] Re: Boot from ISO - exFAT support missing
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906081] [NEW] grub failed to update on reinstall from 20.10 media, 20.04 installs without issue.
Public bug reported: Lenovo thinkpad T500 Model 2081CTO, second attempt from new media. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 21:00:05 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu ** Attachment added: "compressed logs as requested" https://bugs.launchpad.net/bugs/1906081/+attachment/5438878/+files/bug_report_logs.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906081 Title: grub failed to update on reinstall from 20.10 media, 20.04 installs without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Verified on Groovy, same steps and same hardware environment as #4, it worked well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905214] Re: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update
Reply #10 and #11: I found only power-off/power-on is not enough to make the kernel reload the BT firmware on some desktop machines or AIO machines, need to power off, wait for a couple of minutes, power on. For laptop machines, looks like power-off/power-on could make the kernel reload the BT firmware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905214 Title: linux-firmware: intel AX200 (8087:0029) and AX201(8087:0026) bluetooth firmware update To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906067] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1906067 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906079] [NEW] Both ethernet and wifi not working after upgrade from ubuntu 18 to 20
Public bug reported: I have a problem where I cannot use wifi or ethernet. I was going to try this answer: https://unix.stackexchange.com/questions/416180/ubuntu-no- wifi-adapter-found/423250#423250 But I can't get usb tethering to work, so I made a post here: https://unix.stackexchange.com/questions/621883/cannot-use-usb- tethering-to-solve-problem I recently installed Ubuntu 20.04 and this started happening. Not exactly sure which package is responsible here. I am making this bug report on the same pc except I am using an ubuntu installation thumbdrive. The live usb seems to recognize ethernet right away, but the one installed on my ssd doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.29 ProcVersionSignature: Ubuntu 5.4.0-1029.31-gcp 5.4.65 Uname: Linux 5.4.0-1029-gcp x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 21:09:59 2020 InstallationDate: Installed on 2020-10-12 (47 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-11-27 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906079 Title: Both ethernet and wifi not working after upgrade from ubuntu 18 to 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906067] Re: Boot from ISO - exFAT support missing
Exfat support is not a question of ubuntu-cdimage, but of the kernel. ** Project changed: ubuntu-cdimage => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906067] [NEW] Boot from ISO - exFAT support missing
You have been subscribed to a public bug: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Boot from ISO - exFAT support missing https://bugs.launchpad.net/bugs/1906067 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900362] Re: Kernel turns off USB-devices
I started noticing this today after a reboot (kernel 5.8.0-25 hirsute/dev repos). Both my keyboard and mouse have begun autosuspending after only a few seconds on non-use. Echoing 'on' to the appropriate /sys/bus/usb/devices/usb#/#-#/power/control path gets them working again. This is a desktop with no laptop tools / power management packages installed. Looks like udev is being too optimistic about what it should shut down. Bus 007 Device 002: ID 0416:a0f8 Winbond Electronics Corp. WHIFTEC Mechanical Gaming Keyboard 汇富特游戏机械键盘 Bus 001 Device 011: ID 1b1c:1b31 Corsair Corsair Vengeance M90 Mouse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900362 Title: Kernel turns off USB-devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898656] Re: Firefox not playing YouTube videos in Virtualbox on Xubuntu
Have tried the development edition and had the same problem. I did not report the problem to bugzilla, because after I tried to access bugzilla, Github threatened to withdraw my access next month for some vague reasons, unless I changed my password. On Tue, 2020-11-24 at 16:07 +, Olivier Tilloy wrote: > If you have some time to spare, could you test whether the upstream > builds (which can be downloaded from > https://www.mozilla.org/firefox/download/thanks) are similarly > affected, > and if so, file an upstream bug report at > https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox ? > > ** Changed in: firefox (Ubuntu) >Status: Incomplete => New > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898656 Title: Firefox not playing YouTube videos in Virtualbox on Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1898656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904914] Re: Xenial update: v4.4.244 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904914 Title: Xenial update: v4.4.244 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904904] Re: Xenial update: v4.4.243 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904904 Title: Xenial update: v4.4.243 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903750] Re: Xenial update: v4.4.242 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903750 Title: Xenial update: v4.4.242 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
Hi Benjamin, No worries about being busy. Now, the kernel is scheduled to be released early next week, around the 30th of November. I think at this stage it is best to wait it out and install the kernel once it reaches -updates. That way you will have a fixed kernel that is supported by livepatch, and you don't have to justify a reboot twice. I did some regression testing in my comments above, and everything looks okay. These patches also worked great in your test kernel. We have done the best can to verify the kernel in the time given, so don't worry about testing at this stage. I'll let you know once the kernel has reached -updates, likely Monday or Tuesday next week. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905048] Re: samba ftbfs in hirsute, needs merge
** Changed in: samba (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905048 Title: samba ftbfs in hirsute, needs merge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1905048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905510] Re: utils-linux 2.36.1 breaks user mounts (cifs)
** Changed in: util-linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905510 Title: utils-linux 2.36.1 breaks user mounts (cifs) To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1905510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support
** Changed in: sssd (Ubuntu Focal) Assignee: (unassigned) => Sergio Durigan Junior (sergiodj) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1905790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Verification for Focal is needed on this bug. Would someone who has tested the fix with focal please complete that? Thank you! This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896642] Re: Request for CIFS patches to be available in 5.4 kernel
Hi @Marcelo - may you please complete the verification? Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896642 Title: Request for CIFS patches to be available in 5.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897963] Re: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode
Hi @Igor, may you please complete the verification? Thank you! This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897963 Title: Cherry Pick needed for Critical upstream patch for Kernel null pointer dereference - usb-c altmode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900855] Re: linux-aws: fold test_bpf SAUCE to linux/master
Hi @Paolo - may you please complete the verification on this? Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900855 Title: linux-aws: fold test_bpf SAUCE to linux/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903420] Re: Qemu clients lose Internet access on upgrade to Groovy Gorilla
To work around this, I used `update-alternatives` to change iptables and ip6tables from iptables-nft to iptables-legacy. At least things function now. (I'm using docker.io and putting RKE's Kubernetes on top of it). It appears that workaround allows the networking to properly work, and also implies that Docker is manipulating the tables using some other method than /usr/sbin/iptables (confirmed in the moby ticket below). I tried starting dockerd with iptables=false, but Kubernetes really needs thorough networking to function. Related tickets: https://github.com/moby/moby/issues/26824 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921600 https://github.com/kubernetes/kubernetes/issues/71305#issuecomment-457573867 https://github.com/kubernetes/kubernetes/pull/82966 ** Bug watch added: github.com/moby/moby/issues #26824 https://github.com/moby/moby/issues/26824 ** Bug watch added: Debian Bug tracker #921600 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921600 ** Bug watch added: github.com/kubernetes/kubernetes/issues #71305 https://github.com/kubernetes/kubernetes/issues/71305 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903420 Title: Qemu clients lose Internet access on upgrade to Groovy Gorilla To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1903420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906078] Re: Whoopsie sends bug reports automatically without consent
** Description changed: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": - renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie - renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie - renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie - renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie - new file: systemd/system/multi-user.target.wants/whoopsie.service + renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie + renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie + renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie + renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie + new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... - My /etc/ does a "whoopsie" file (/etc/whoopsie) which doesn't seem to be - present in clean installations of Ubuntu and which there is the + My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem + to be present in clean installations of Ubuntu and which there is the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. ** Description changed: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem - to be present in clean installations of Ubuntu and which there is the + to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I
[Bug 1906078] [NEW] Whoopsie sends bug reports automatically without consent
Public bug reported: Hello, So, I just realized about an hour ago that whoopsie has been sending bug reports without my consent since May (2020-05-11 to be exact) from checking journalctl where I can see lines like these: Uploading /var/crash/[...] Sent; server replied with: No error Response code: 200 Reported OOPS ID [...] I checked the "Diagnostics" GUI in the gnome-control-center and it does have "Send error reports to Canonical" set to "Never"... I tried switching it to "Manual" and back to "Never" and that did have an effect in /etc/, namelely when going from "Never" to "Manual": renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie new file: systemd/system/multi-user.target.wants/whoopsie.service and the opposite effect is achieved when switching back to "Never". So far so good, I guess... My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't seem to be present in clean installations of Ubuntu and which has the following contents: [General] report_metrics=true Switching from "true" to "false" does seem to disable whoopsie, so that's nice I guess... but what is this file doing here in the first place? To clarify, this was originally an Ubuntu 18.04 system which I recently upgraded to 20.04 but the unsolicited error report uploads have been going on since well before the upgrade so that's not the issue. I don't remember touching anything on my system relating to apport or whoopsie and my shell history doesn't contain anything about whoopsie or apport so this situation seems to have occurred on its own (perhaps after an update?). This is a pretty serious breach of privacy (and of the GDPR) and others might also be unknowingly affected like I was, so the team in charge of this might want to push an update that for instance resets the /etc/whoopsie file if present (if that truly is the problem). While I'm at it I would like all the error reports sent from my computer to be deleted. Where can I ask for that? I haven't seen an option for that anywhere, apart from contacting dataprotect...@canonical.com. Best regards. ** Affects: whoopsie (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/1906078 Title: Whoopsie sends bug reports automatically without consent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1906078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906076] [NEW] Upgrade to 20.04 fails "Could not calculate the upgrade"
Public bug reported: Looking at the apt.log would seem to indicate that the upgrade fails somewhere when investigating python. I have removed all PPAs as far as I can tell, so that shouldn't be the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 18:37:19 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-27 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906076 Title: Upgrade to 20.04 fails "Could not calculate the upgrade" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1906076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906074] Re: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906074 Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1906074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906074] [NEW] package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128
Public bug reported: Attempted to uninstall AisleRiot Solitaire which was preinstalled with Ubuntu 20.04. Received an error that the process was locked by aptd, rebooted, retried, crashed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2020d-0ubuntu0.20.04 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 18:25:55 2020 DuplicateSignature: package:tzdata:2020d-0ubuntu0.20.04 Setting up tzdata (2020d-0ubuntu0.20.04) ... Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 128 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-11-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906074 Title: package tzdata 2020d-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1906074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906075] [NEW] executing 'grub-install /dev/sdc' failed. This is a fatal error
Public bug reported: Using live USB to install which at the fag end of the installation shows this error message saying the installer has crashed. But I also see another modal window with message "Installation is complete. You need to restart the computer in order to use the new installation. "Restart Now" button. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 23:28:53 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base linux-base linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906075 Title: executing 'grub-install /dev/sdc' failed. This is a fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1906075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Problems appear with changs on drivers for/and screen resolution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901344] Re: [SRU] Spotify album icon shows optimal CD disk instead of album/cover image
** Description changed: The Spotify Album Icon in the Sound Applet should show the Album/Song cover of the Spotify song. Instead it shows the default CD icon. According to upstream, the Spotify link has changed. A fix for this (and in the cinnamon-screensaver) is available. An SRU for BOTH PACKAGES, cinnamon, and cinnamon-screensaver in Focal and Groovy is required. (4 projects, 2 packages, 2 versions) SRU Template: - [Impact] + [Impact] - * When users are playing a Song via Spotify: - * Cinnamon Package: In the sound applet, the Spotify album cover should show, but instead the plain 'CD'/Disk icon shows. - * Cinnamon Screensaver Package: On the top left, the song information, including the album cover should show but the album cover doesn't appear. + * When users are playing a Song via Spotify: + * Cinnamon Package: In the sound applet, the Spotify album cover should show, but instead the plain 'CD'/Disk icon shows. + * Cinnamon Screensaver Package: On the top left, the song information, including the album cover should show but the album cover doesn't appear. [Test Case] - * Cinnamon Package: Play a song via Spotify and open the Sound applet to see the CD/Disk icon rather than the album. - * Cinnamon Screensaver Package: Play a song via Spotify and lock the screen to see no album on the top left when you unlock when it asks for password input. + * Cinnamon Package: Play a song via Spotify and open the Sound applet to see the CD/Disk icon rather than the album. + * Cinnamon Screensaver Package: Play a song via Spotify and lock the screen to see no album on the top left when you unlock when it asks for password input. [Regression Potential] - * Regressions through other Spotify updates, or any link updates (the + * Regressions through other Spotify updates, or any link updates (the main cause of this bug) can cause possible regression. - * Python is always known for breaking compatibility with plugins and + * The main cause of this bug was broken links-so another link change + can also cause regression, so this may need to be SRU'd again sometime + in the future. + + * Python is always known for breaking compatibility with plugins and such; while this is unlikely if it were to happen, it probably shouldn't happen before the support for Focal/Groovy expires. - * Physically talking Regression Potential: Very low. This was applied - upstream in Linux Mint recently. I will make sure this is fixed when it - waits in -proposed before it moves officially. + [Other Info] - [Other Info] - - * This package requires a patch for BOTH Focal and Groovy. - * Review the Focal patch first before we move onto the Groovy patch - * Both will be tested. + * This package requires a patch for BOTH Focal and Groovy. + * Review the Focal patch first before we move onto the Groovy patch + * Both will be tested. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cinnamon 4.6.7-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Sat Oct 24 15:10:36 2020 InstallationDate: Installed on 2020-10-23 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cinnamon 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/1901344 Title: [SRU] Spotify album icon shows optimal CD disk instead of album/cover image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1901344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906073] [NEW] Syslog generates an error per second - appears to be related to Discord notification icons
Public bug reported: My computer recently stopped booting due to a 50GB+ syslog file, so I've had the syslog open in a terminal to follow any errors that repeat. Whilst on a call to some friends I noticed that the following error would generate once per second within the syslog file: Nov 27 23:02:36 jared-MS-7930 ubuntu-appindicat...@ubuntu.com[2305]: discord1, Impossible to lookup icon for 'discord1_53-panel' Nov 27 23:02:36 jared-MS-7930 gnome-shell[2305]: JS ERROR: Exception in callback for signal: icon: Error: Argument 'filename' (type filename) may not be null#012_createIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:406:26#012_cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:368:14#012_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:574:18#012_updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:601:14#012_emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47#012_onPropertiesChanged/<@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:220:22#012_onPropertiesChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:214:15#012refreshPropertyOnProxy/<@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:51:19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 23:04:20 2020 InstallationDate: Installed on 2014-12-07 (2182 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-09-29 (59 days ago) ** Affects: gnome-shell-extension-appindicator (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/1906073 Title: Syslog generates an error per second - appears to be related to Discord notification icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1906073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891953] Re: CVE-2019-8936
@alexmurray - The debdiff for Groovy is identical to the one from Focal (same source package version). Let me know if you need a distinct debdiff with the release pocket (groovy-security) identified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891953 Title: CVE-2019-8936 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904613] Re: Bionic update: upstream stable patchset 2020-11-17
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904613 Title: Bionic update: upstream stable patchset 2020-11-17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904791] Re: Bionic update: upstream stable patchset 2020-11-18
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904791 Title: Bionic update: upstream stable patchset 2020-11-18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904884] Re: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904884 Title: s390: dbginfo.sh triggers kernel panic, reading from /sys/kernel/mm/page_idle/bitmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1904884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905333] Re: Bionic update: upstream stable patchset 2020-11-23
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905333 Title: Bionic update: upstream stable patchset 2020-11-23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906072] [NEW] Out-of-tree modules no longer build since 596b0474d3d9 in 5.10-rc1
Public bug reported: Hi, See these for reference: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 - https://lore.kernel.org/lkml/cah2r5msnpjeabv2er7anqrsde-9vyrznsdif0+odojayl_a...@mail.gmail.com/ (and the other messages in the thread - https://github.com/openSUSE/kernel-source/commit/fe37c160c33dc09edff1781810aa098a2c316e20 Building nvidia under 5.10-rc1 or later fails, because of commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=596b0474d3d9b1242eab713f84d8873f9887d980 ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #975571 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 ** Also affects: linux via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571 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/1906072 Title: Out-of-tree modules no longer build since 596b0474d3d9 in 5.10-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1906072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903768] Re: Bionic update: upstream stable patchset 2020-11-10
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903768 Title: Bionic update: upstream stable patchset 2020-11-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906070] [NEW] No "minimum partition size" warning before install !
Public bug reported: Installer does NOT tell the minimum size for partitions during install. Installer always suggests minimum space for partitions 10GB, but this makes no sense ! Installer does accept partition sizes when pressing install, but fails on "Insufficient space" ! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-lowlatency 5.4.65 Uname: Linux 5.4.0-53-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperVersion: 1.445.1 Date: Fri Nov 27 23:19:44 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper file=/cdrom/preseed/ubuntustudio.seed fsck.mode=skip quiet splash --- LiveMediaBuild: JamulusOS v2.00-EN amd64 "Custom Focal Fossa" (20201113) 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.2 ubuntustudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906070 Title: No "minimum partition size" warning before install ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1906070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891953] Re: CVE-2019-8936
Patch for Focal ** Patch added: "Patch for Focal" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+attachment/5438836/+files/1-ntp_4.2.8p12+dfsg-3ubuntu5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891953 Title: CVE-2019-8936 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532264] Re: fprintd allows unauthorized root access
Thanks for explaining the larger problem here. It's a bit frustrating that this bug has existed for more than 9 years, (it seems the original fix was put in in 2011), but it's taken this long to finally swat it. Sounds like we're finally on the right path to getting this fixed. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532264 Title: fprintd allows unauthorized root access To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1532264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832182] Autopkgtest regression report (apache2/2.4.41-4ubuntu3.2)
All autopkgtests for the newly accepted apache2 (2.4.41-4ubuntu3.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: plinth/20.3 (s390x) munin/2.0.56-1ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#apache2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901755] Re: "btrfs subvolume list" sporadically segfaults with linux-image-5.4.0-52-generic
I'm still getting this error on Ubuntu 18.04 with kernel 5.4.0-54.60. Installed Mainline Kernel 5.9.10 as a workaround... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901755 Title: "btrfs subvolume list" sporadically segfaults with linux- image-5.4.0-52-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438835/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438834/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438833/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438831/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438832/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438830/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438829/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905993 Title: Actual kernel don't want to make more than 64 cpus available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905993] Re: Actual kernel don't want to make more than 64 cpus available
apport information ** Tags added: apport-collected bionic uec-images ** Description changed: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.20 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + Tags: bionic uec-images + Uname: Linux 4.19.160-0419160-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1905993/+attachment/5438828/+files/ProcCpuinfoMinimal.txt ** Description changed: This is kinda complicated but i try my best to explain it as much as i can. First of all i found out that in bionic beaver cloud image i was able to have 248 cpus without any issues. Then i've taken a look into focal, but there i was only able to get up up to 64 cpus. Then i've tryed to figure out what was wrong. Debian, wasnt able to handle this with a 4.19 kernel. Bionic beaver had 4.18 so i tried to upgrade to a 4.19 with success but only with 64 cpus. So i think the problem maybe exist since 4.19. My setup. Openstack Hypervisor with ubuntu 18.04 KVM/Qemu with a vm clean bionic works fine, till i upgrade to a kernel > 4.18. Every 5.* version seems to be affected as well. Debian buster has this issue and fedora (Both in latest versions with kernel above 4.18) Already started debugging with TJ- at irc. Paste links with debugging informations /sys/devices/system/cpu/cpu*/topology/ http://paste.ubuntu.com/p/5txHGPHpBT/ and virsh dumpxml of the VM https://pastebin.ubuntu.com/p/sPWHVMn5FX/ CPU on the Hypervisor (works fine): https://pastebin.ubuntu.com/p/KRNMSThT92/ Hope this helps to dig down the bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Tags: bionic uec-images Uname: Linux 4.19.160-0419160-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Nov 27 21:50 seq + crw-rw 1 root audio 116, 33 Nov 27 21:50 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.20 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: OpenStack Foundation OpenStack Nova + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-63-generic root=UUID=17d2bcf1-3687-426a-8219-978743746d51 ro console=tty1 console=ttyS0 + ProcVersionSignature: Ubuntu 5.0.0-63.69-generic 5.0.21 +
[Bug 1905790] Re: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support
> While the change may involve quite different code paths when it comes to security features, I think we trust OpenSSL enough to be an acceptable crypto backend. And behavior should not change. Are you sure about this? TLS has a wide variety of protocol options and the supported vs. "available" cryptosystem matrix is complex. Won't these all change if the underlying implementation changes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905790 Title: Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1905790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
debdiff for hirsute in attach. ** Patch added: "hirsute-zfs-fix-double-free-with-zfs-mount.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438827/+files/hirsute-zfs-fix-double-free-with-zfs-mount.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901248] Re: Please build the package as upstream does Edit
*** This bug is a duplicate of bug 1900897 *** https://bugs.launchpad.net/bugs/1900897 ** Changed in: google-osconfig-agent (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** This bug has been marked a duplicate of bug 1900897 Please build the package as upstream does -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901248 Title: Please build the package as upstream does Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/1901248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832182] Autopkgtest regression report (apache2/2.4.46-1ubuntu1.1)
All autopkgtests for the newly accepted apache2 (2.4.46-1ubuntu1.1) for groovy have finished running. The following regressions have been reported in tests triggered by the package: nova/unknown (armhf) lemonldap-ng/2.0.8+ds1-2 (arm64) gvfs/1.46.1-1ubuntu1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apache2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
I have a similar problem. I have Ubuntu Studio 20.04 installed. The included Memtest86+ 5.01 freezes at 55% on test #2 every single time. Memtest86+ 4.20 from an Ubuntu 14.04 DVD passes without error. Memtest86+ 5.31b downloaded and burned to a CD-RW passes without error. I have also encountered the issue where Memtest86+ 5.01 freezes on many machines with SMP activated. I do not trust v5.01 to give reliable results any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905986] Re: Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead
** Description changed: [Impact] * gce-compute-image-packages has been split to multiple source packages and google-guest-agent (written in Go) replaced the services originally written in Python. The upgrade to gce-compute-image-packages compatible with google-guest-agent replaced the Python modules (python3-google-compute-engine) with an empty transitional package. The removal of the modules could break local software relying on those modules. * The fix is not providing the empty python3-google-compute-engine transitional package, but adding Breaks: to google-guest-agent to force the removal of it. Since removals are not performed automatically by apt-get upgrade (not unattended-upgrades) the administrator needs to approve removal. [Test Case] * Set up a system with the unfixed version of the packages, including python3-google-compute-engine installed. * Upgrade to the new set of packages: apt-get upgrade * Observe that the gce-compute-image-packages is kept back * Upgrade gce-compute-image-package manually: apt install gce-compute-image-package * This should succeed, removing python3-google-compute-engine Dist-upgrade from Trusty: TODO [Where problems could occur] - * The packages may become uninstallable upon upgrade or dist-upgrade. Testing was performed to avoid such regressions. - Since the aim of this fix is preventing accidental upgrades should a security update of the affected packages be released the fix will prevent automatic application of this updated. In such case the the transitional package can be reintroduced and the Breaks: can be converted to a versioned Breaks: on the non-transitional package versions. + * The packages may become uninstallable upon upgrade or dist-upgrade. + Testing was performed to avoid such regressions. + + * Since the aim of this fix is preventing accidental upgrades should a + security update of the affected packages be released the fix will + prevent automatic application of this updated. In such case the the + transitional package can be reintroduced and the Breaks: can be + converted to a versioned Breaks: on the non-transitional package + versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905986 Title: Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1905986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905986] Re: Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead
** Description changed: [Impact] - * gce-compute-image-packages has been split to multiple source packages and google-guest-agent (written in Go) replaced the services originally written in Python. The upgrade to gce-compute-image-packages compatible with google-guest-agent replaced the Python modules (python3-google-compute-engine) with an empty transitional package. The removal of the modules could break local software relying on those modules. - * The fix is not providing the empty python3-google-compute-engine transitional package, but adding Breaks: to google-guest-agent to force the removal of it. Since removals are not performed automatically by apt-get upgrade (not unattended-upgrades) the administrator needs to approve removal. + * gce-compute-image-packages has been split to multiple source packages and google-guest-agent (written in Go) replaced the services originally written in Python. The upgrade to gce-compute-image-packages compatible with google-guest-agent replaced the Python modules (python3-google-compute-engine) with an empty transitional package. The removal of the modules could break local software relying on those modules. + * The fix is not providing the empty python3-google-compute-engine transitional package, but adding Breaks: to google-guest-agent to force the removal of it. Since removals are not performed automatically by apt-get upgrade (not unattended-upgrades) the administrator needs to approve removal. [Test Case] - * Set up a system with the unfixed version of the packages, including python3-google-compute-engine installed. - * Upgrade to the new set of packages: -apt-get upgrade - * Observe that the gce-compute-image-packages and python3-google-compute-engine packages are kept back. - * Upgrade google-compute-engine manually: -apt install google-compute-engine - * This should succeed, removing python3-google-compute-engine + * Set up a system with the unfixed version of the packages, including python3-google-compute-engine installed. + * Upgrade to the new set of packages: + apt-get upgrade + * Observe that the gce-compute-image-packages is kept back + * Upgrade gce-compute-image-package manually: + apt install gce-compute-image-package + * This should succeed, removing python3-google-compute-engine - Dist-upgrade from Trusty: - TODO + Dist-upgrade from Trusty: + TODO [Where problems could occur] - * TODO + * The packages may become uninstallable upon upgrade or dist-upgrade. Testing was performed to avoid such regressions. + Since the aim of this fix is preventing accidental upgrades should a security update of the affected packages be released the fix will prevent automatic application of this updated. In such case the the transitional package can be reintroduced and the Breaks: can be converted to a versioned Breaks: on the non-transitional package versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905986 Title: Don't provide transitional package for python3-google-compute-engine, add Breaks: in google-guest-agent instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1905986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906064] [NEW] RTL8812AE stops using 5 Ghz due to wpa_supplicant 4 way key_mgmt_offload
Public bug reported: On Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-53-generic x86_64) RTL8812AE stops using 5 Ghz Wifi after a few days. The 2.4 Ghz wifi (that was not used, but present in these days) kept working. During reconnection, the 4-way Wifi authentication failed every time. Usually, power down and up helps, but this did not give me additional information I tried following, to no avail 1) stopping / restarting wifi from networkmanager 2)removing drivers, and reinstalling sudo rmmod rtl8821ae btcoexist rtl_pci rtlwifi mac80211 cfg80211 libarc4 sudo modprobe rtl8821ae 3) restart wpa_supplicant sudo systemctl restart wpa_supplicant.service 4) restart networkmanager sudo service NetworkManager restart What fixed the problem was disabling key_mgmt_offload sudo wpa_cli set key_mgmt_offload 0 So apparently, the WiFi board froze into a state where the 4-way Wifi authentication could not be handled on the board itself anymore ** Affects: wpasupplicant (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-flashback (Ubuntu) => wpasupplicant (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906064 Title: RTL8812AE stops using 5 Ghz due to wpa_supplicant 4 way key_mgmt_offload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1906064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832182] Autopkgtest regression report (apache2/2.4.29-1ubuntu4.15)
All autopkgtests for the newly accepted apache2 (2.4.29-1ubuntu4.15) for bionic have finished running. The following regressions have been reported in tests triggered by the package: ubuntuone-dev-tools/13.10-0ubuntu6 (amd64) pinto/0.97+dfsg-4ubuntu1 (arm64) cacti/1.1.38+ds1-1 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#apache2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905322] Re: LibreOffice crashes under load.
Alright, open all the LibreOffice apps one by one - do it in order. When you open Impress, Math and Writer do NOT open. In Impress, select a template and click Okay. Everything LibreOffice related crashes and it gives a dialog about restoring files. I installed ksystemlog (just to make it easier) and triggered the crash multiple times. Nothing shows up in the error logs, though you can clearly see it in the video provided in #7 (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905322/comments/7). That happens time and time again - every time. It happens in a VM on different hardware. It happens in a live USB environment. It happens in today's Hirsute build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905322 Title: LibreOffice crashes under load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905579] Re: parted crashes with invalid pointer on resizepart on focal
** Tags added: seg sts ** Changed in: parted (Ubuntu) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: parted (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905579 Title: parted crashes with invalid pointer on resizepart on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1905579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892949] [ubuntustudio-default-settings/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892949 Title: [SRU] grub can no longer detect kernels after ubuntustudio-lowlatency- settings is uninstalled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-settings/+bug/1892949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902588] Re: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902588 Title: zfs mount -a: double free / memory corruption / segfault when mountpoint of dataset is not empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.
systemctl --user status pulseaudio.service ** Attachment added: "systemctl --user status pulseaudio.service" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5438826/+files/systemctl_--user_status_pulseaudio.service.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902580 Title: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545320] Re: Dell XPS13 with i915 hangs with only mouse cursor and SSH working
No longer an issue on Ubuntu kernel 4.15.0-124-generic ** Changed in: linux (Ubuntu) Status: Triaged => 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/1545320 Title: Dell XPS13 with i915 hangs with only mouse cursor and SSH working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1545320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906062] [NEW] failed to install ubuntu 20.10, grub install failed
Public bug reported: trying to install ubuntu with bootable usb drive made using disk creator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 Date: Fri Nov 27 15:04:49 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-29-generic linux-base linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906062 Title: failed to install ubuntu 20.10, grub install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1906062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906061] [NEW] vim package links against libcanberra
Public bug reported: vim 8.1 and newer has decided to link against libcanberra for "sound support", which pulls in several other reasonably unnecessary packages (libasound2, libvorbis to name a couple) for server environments. Presumably the --disable-canberra flag should be applied on configure. Focal+, as far as I can tell. See also https://bugs.archlinux.org/task/63073 ** Affects: vim (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/1906061 Title: vim package links against libcanberra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1906061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532264] Re: fprintd allows unauthorized root access
As you can see reading this old bug, the polkit rule fix is known, and I've been working upstream to address this. However as you can see [1] that simple change was not enough. In fact as you can read in this documentation [2] the polkit method that we call to check if an user is allowed to run a command, is run synchronously and this may lead fprintd to hang and stop doing other operations (that can be both in the driver or for other requests coming by other users). So, while the workaround can be acceptable in a single-user and single- request scenario, it could end up having problems in case the OS tries to do other requests to the fingerprint daemon while it's blocked. A situation could be that if you start the enrollment process and for some reason you don't complete within the auto-screen-lock time, then you may end up in freezing your system. Or in any other case... Fprintd is meant to be called by multiple applications other than the OS (even if right now very few use it), but ideally a Browser or an application may request you to use your fingerprint, and that could happen while the daemon is hanging, causing an unexpected behavior. Said that, as you can see the fix is merged and released in latest fprintd version that I'm currently packaging and soon backporting to 20.04, so even if with some delay we're handling this. Properly, finally. [1] https://gitlab.freedesktop.org/libfprint/fprintd/-/merge_requests/74 [2] https://www.freedesktop.org/software/polkit/docs/latest/PolkitAuthority.html#polkit-authority-check-authorization-sync -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532264 Title: fprintd allows unauthorized root access To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1532264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906059] [NEW] Gnome calendar mishandles timezone during moving across calendars
Public bug reported: Steps to reproduce: 1. Make calendar entry in gnome-calendar in Personal(not online) calendar. To be precise I've imported calendar entry via ICS file via Evolution but the file didn't contain any time zone related entry. 2. Calendar was properly introduced showing me locally proper time of event, in line with my local timezone. 3. Open calendar entry by double click, change on upper bar name of calendar from personal to one of Google Calendars . 4. Time of event is shifted In my case time of the shift is -1 hour . This corresponds my current timezone GMT+1 so it seems item is passed without timezone resulting in UTC time presented as local. Additionally when I shift time of event during editing by one minute then there is no hour shift so it seems error is generated exactly in this dialog box but only for imported entries - if I create new one manually then it works properly. So for reproducing, this is content of the ICS file with personal details scraped out: BEGIN:VCALENDAR VERSION:2.0 BEGIN:VEVENT URL:https://example.com/path/ DTSTART:20201128T11Z DTEND:20201128T114500Z SUMMARY:[A] - IN CASE THIS AMPERSAND COULD HAVE ANY IMPORTANCE I LEAVE IT DESCRIPTION:By Wojciech Lesicki LOCATION:https://example.com END:VEVENT END:VCALENDAR ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 20:16:33 2020 InstallationDate: Installed on 2015-05-08 (2030 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to bionic on 2018-08-26 (823 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906059 Title: Gnome calendar mishandles timezone during moving across calendars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1906059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852935] Re: In Ubuntu Budgie, QT apps take a long time to open
*** This bug is a duplicate of bug 1851160 *** https://bugs.launchpad.net/bugs/1851160 Same problem on fresh Ubuntu 20.04. It seems the dbus is a problem. Launching applications wth the command: dbus-launch vls, starts apps intermediately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852935 Title: In Ubuntu Budgie, QT apps take a long time to open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1852935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
