[Bug 1850162] Re: Akonadi server will not start after upgrade to kubuntu 19.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: akonadi (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/1850162 Title: Akonadi server will not start after upgrade to kubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1850162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849426] Re: Daily Limit Exceeded error for Google calendar
Same problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849426 Title: Daily Limit Exceeded error for Google calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1849426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854552] [NEW] Failed to load the selected library 'std.cfg'. File not found
Public bug reported: cppcheck-gui is installable without cppcheck - and this configuration actually works. But the required file std.cfg is missing in this case leading to the following error message: Failed to load the selected library 'std.cfg'. File not found => Perhaps the solution would be to split this file into a separate package named cppcheck-common. But an own package for one simple file feels a bit strange. ** Affects: cppcheck (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/1854552 Title: Failed to load the selected library 'std.cfg'. File not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cppcheck/+bug/1854552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785912] Re: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV
** Changed in: linux Status: Incomplete => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #166 https://gitlab.freedesktop.org/drm/intel/issues/166 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785912 Title: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1785912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785912]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/166. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785912 Title: Horizontal screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1785912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I experience this problem only with WPS office under Ubuntu 19.10. I usually need to copy text twice in order to send it to clipboard. Because copy option is actually broken, it happens that the previous text is pasted (not the one I copied). However, other programs work just fine most of the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (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/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
*** This bug is a duplicate of bug 1845046 *** https://bugs.launchpad.net/bugs/1845046 Thanks for the bug report and sorry I was on vacation when you emailed me about bug 1724919. Now that you mention Sony WH-1000XM3 I realize this is actually bug 1845046 which also was first reported against Sony WH-1000XM3. ** This bug has been marked a duplicate of bug 1845046 Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853550] Re: lubuntu 20.04 live daily; unable to make use of virtual keyboard
Sorry @sudodus - I didn't see this earlier (another test on that box had me look here looking for bug ID) I attempt to use 'live' media using only included software, or if I need to add packages I need to be able to do without touching the keyboard since I use this device as if tablet only (on screen keyboard being needed so I can connect to wifi..). I'm using the `fcitx` keyboard (or whatever it starts); which I CAN make appear, but I cannot get the keys I touch on it, to appear in the wifi qterminal box to connect to wifi etc. Same issue again today, current daily on motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series). I did the same thing using today's Xubuntu 20.04 today; onboard allowed me to complete this test there :) This issue is really MINOR, as I'd just attach a keyboard in real life; and then connect wifi, or if I wasn't allowed to do that, connect an ethernet cable... (`onboard` appears in `muon package manager`; I looked) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853550 Title: lubuntu 20.04 live daily; unable to make use of virtual keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1853550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853550] Re: lubuntu 20.04 live daily; unable to make use of virtual keyboard
It maybe the problem is me (user not knowing how to use fcitx keyboard). It seems to get stuck on 'move' mode as if I'm not careful when trying to hit a key it 'moves' the keyboard around (thus it's not in entry mode). My attempts to get around this have failed. I installed `onboard`; and could use it's onscreen keyboard without issue. If I was on a device without ethernet though; I'd need onscreen keyboard to work to enter my wifi's key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853550 Title: lubuntu 20.04 live daily; unable to make use of virtual keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1853550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
** Changed in: yaru Status: New => 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/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770268] Re: [GeForce GTX 1080] 18.04 DisplayPort 15m cable no display
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (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/1770268 Title: [GeForce GTX 1080] 18.04 DisplayPort 15m cable no display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846006] Re: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-installed')
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (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/1846006 Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1846006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844860] Re: [nouveau] Freezing system
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1844860 Title: [nouveau] Freezing system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1844860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845729] Re: problem to print and to scan
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1845729 Title: problem to print and to scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845541] Re: OS becomes unresponsive when power is plugged in and battery is low
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1845541 Title: OS becomes unresponsive when power is plugged in and battery is low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844906] Re: gnome-shell crash after suspend
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1844906 Title: gnome-shell crash after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845356] Re: decolorisation on my laptop display
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1845356 Title: decolorisation on my laptop display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844609] Re: my screen flickering
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: 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/1844609 Title: my screen flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1844609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845076] Re: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1845076 Title: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845076] Re: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (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/1845076 Title: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845966] Re: Conflicts between std::byte and byte
[Expired for gcc-mingw-w64 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gcc-mingw-w64 (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/1845966 Title: Conflicts between std::byte and byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-mingw-w64/+bug/1845966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash for "No space left on device"
Filed a question within nvidia forum: https://devtalk.nvidia.com/default/topic/1066963/linux/if-laptop-lid-is- closed-during-suspend-quot-failed-to-set-mode-no-space-left-on-device- quot-upon-resume/post/5406357/ so far no closure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850439] Re: No sound on ASUS UX534FT
I have the same issue on Ubuntu with Windows 10 dual boot and kernel 5.4.0 More info: System:Host: Kernel: 5.4.0-050400-generic x86_64 bits: 64 gcc: 9.2.1 Desktop: Gnome 3.28.4 (Gtk 3.22.30-1ubuntu4) Distro: Ubuntu 18.04.3 LTS Machine: Device: laptop System: ASUSTeK product: ZenBook UX534FTC_UX534FT v: 1.0 serial: N/A Mobo: ASUSTeK model: UX534FTC v: 1.0 serial: N/A UEFI: American Megatrends v: UX534FTC.300 date: 09/05/2019 BatteryBAT0: charge: 55.7 Wh 79.1% condition: 70.4/71.0 Wh (99%) model: ASUSTeK ASUS status: Discharging CPU: Quad core Intel Core i5-10210U (-MT-MCP-) arch: Kaby Lake rev.12 cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 16799 clock speeds: max: 4200 MHz 1: 3900 MHz 2: 3900 MHz 3: 3900 MHz 4: 3900 MHz 5: 3900 MHz 6: 3899 MHz 7: 3900 MHz 8: 3901 MHz Graphics: Card-1: Intel Device 9b41 bus-ID: 00:02.0 Card-2: NVIDIA Device 1f91 bus-ID: 02:00.0 Display Server: x11 (X.Org 1.20.4 ) drivers: i915,nouveau Resolution: 1920x1080@60.00hz, 1080x2160@50.03hz, 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics (Comet Lake 3x8 GT2) version: 4.5 Mesa 19.0.2 Direct Render: Yes Audio: Card Intel Device 02c8 driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k5.4.0-050400-generic Network: Card: Intel Device 02f0 driver: iwlwifi bus-ID: 00:14.3 IF: wlo1 state: up speed: N/A duplex: N/A mac: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1850439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853449] Re: gajim-omemo plugin is out of date
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gajim-omemo (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/1853449 Title: gajim-omemo plugin is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1853449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853449] Re: gajim-omemo plugin is out of date
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 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/1853449 Title: gajim-omemo plugin is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1853449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854395] Re: apachectl configtest segmentation fault
Hmm, sorry for putting you on the wrong path there. We'll now need to wait for a developer / package maintainer to have a look at this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854395 Title: apachectl configtest segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1854395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759856] Quick Favor?
Hey, I just signed the petition "Indian Judiciary: Hang the criminal(s) of Priya Reddy Rape/Murder case before the 2019 year end" and wanted to see if you could help by adding your name. Our goal is to reach 7,500 signatures and we need more support. You can read more and sign the petition here: http://chng.it/BmhGJmpmqx Thanks! Ranajit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759856 Title: System crash during installation. Grub installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1759856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
I have ubuntu 19.10 with the latest kernel. I have the same issue with Hp spectre x360. nvme i7-9750h. When is the fix going to be in the 5.3 or 5.4 kernel. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
On 2019/11/29 下午11:15, Mark Dunn wrote: > short version: > > With raspberry pi 4: > your binaries applied (https://people.canonical.com/~hwang4/v3d-fix/) > The screen flickers then blanks > I installed an built the latest mesa > The screen flickers then blanks > Back to the raspberry pi kernel (4.19) > Which still works... > > long version: > > downloaded ubuntu-19.10-preinstalled-server-arm64+raspi3.img and > restored it to sdcard > > sudo apt update > sudo apt upgrade > sudo apt install ubuntu-desktop > > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > > sudo dpkg -i linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > sudo dpkg -i linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > sudo dpkg -i linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > > sudo dpkg -i linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > linux-headers-5.3.0-1013-raspi2 depends on linux-raspi2-headers-5.3.0-1013; > however: >Package linux-raspi2-headers-5.3.0-1013 is not installed. > sudo apt --fix-broken install > The following packages will be REMOVED: >linux-headers-5.3.0-1013-raspi2 > > sudo reboot > sudo apt-get install mesa-utils > > glxinfo -B > > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > Extended renderer info (GLX_MESA_query_renderer): > Vendor: Broadcom (0x14e4) > Device: V3D 4.2 (0x) > Version: 19.2.1 > Accelerated: yes > Video memory: 3791MB > Unified memory: yes > Preferred profile: compat (0x2) > Max core profile version: 0.0 > Max compat profile version: 2.1 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 3.0 > OpenGL vendor string: Broadcom > OpenGL renderer string: V3D 4.2 > OpenGL version string: 2.1 Mesa 19.2.1 > OpenGL shading language version string: 1.20 > > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 > > glxgears > > Running synchronized to the vertical refresh. The framerate should be > approximately the same as the monitor refresh rate. > 348 frames in 5.0 seconds = 69.440 FPS > 247 frames in 5.0 seconds = 49.358 FPS > 301 frames in 5.0 seconds = 60.029 FPS > 301 frames in 5.0 seconds = 60.019 FPS > 300 frames in 5.0 seconds = 59.999 FPS > 300 frames in 5.0 seconds = 59.992 FPS > 256 frames in 5.0 seconds = 51.041 FPS > 300 frames in 5.0 seconds = 59.989 FPS > 301 frames in 5.0 seconds = 60.011 FPS > X connection to :0 broken (explicit kill or server shutdown). Are your sure you booted the system with the v3d-fix kernel? I remember with that kernel, the glxgears at least could run without crash or system hang, of course the v3d-fix has some other problems. So could you please run 'uname -a' to check the kernel you are running? And our plan is to disable this driver temporarily, we will report bug to usptream against rpi-5.3.y, and we will look for fixes from 4.19 branch too. Thanks, Hui. > > Eventually screen starts to flicker then blanks... > built and installed latest mesa - no change > > sudo nano /etc/apt/sources.list (commented in all sources) > sudo apt update > sudo apt-get build-dep mesa > > mkdir git > cd git > sudo apt-get build-dep mesa > sudo apt-get install -y pkg-config bison flex > > git clone https://gitlab.freedesktop.org/mesa/drm.git > cd drm > meson build --prefix=/usr --libdir=/usr/lib/aarch64-linux-gnu > ninja -C build > sudo ninja -C build install > cd .. > > git clone https://gitlab.freedesktop.org/mesa/mesa.git > cd mesa > meson build \ > --prefix=/usr \ > --libdir=/usr/lib/aarch64-linux-gnu \ > -Dbuildtype=release \ > -Dplatforms=x11,drm,surfaceless \ > -Ddri-drivers= \ > -Dgallium-drivers=vc4,v3d,kmsro > ninja -C build > sudo ninja -C build install > > sudo reboot > > flickers and then blanks :( > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
@gregordarius is it possible to apply this patch on your own? could you post more detailed instructions? I am having exactly the same error as you and I can solve it with all the ways you mentioned before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1843695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854542] Re: Install of ubuntu 19.10 crashed during file copying with "faulty CD or HDD" although I installed from a good USB stick onto a good SSD
Thank you for taking the time to report this issue and helping to make Ubuntu better. This package failure looks like it was caused by bad ISO download, corrupted install media, or device failure. eg. look in the logs and you'll see messages like these :- Nov 29 21:14:24 ubuntu kernel: [ 265.105029] SQUASHFS error: zlib decompression failed, data probably corrupt Nov 29 21:14:24 ubuntu kernel: [ 265.105031] SQUASHFS error: squashfs_read_data failed to read block 0x524c0 Examining the information you have given us, this does not appear to be a useful bug report so I am closing it, as it appears to be a bad ISO or faulty device (inc.` bad write-to-device). If you believe I'm in error, please leave a comment explaining why and change the status back to 'New'. I suggest you verify your ISO download, and use the 'check disc for defects' option to validate your media before install to ensure a good download & write. Possibly useful : https://tutorials.ubuntu.com/tutorial/tutorial-how-to- verify-ubuntu#0 and https://help.ubuntu.com/community/Installation/CDIntegrityCheck ** Changed in: ubiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854542 Title: Install of ubuntu 19.10 crashed during file copying with "faulty CD or HDD" although I installed from a good USB stick onto a good SSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854545] [NEW] package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: during upgrade the system reported this issue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 18:52:23 2019 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-11-29 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-11-29 (0 days ago) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854545 Title: package grub-efi-amd64-signed 1.93.14+2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1854545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409347]
Created attachment 9285 Fixes reverse horizontal scrolling I've attached a patch that fixes the issue by codifying the solution Razz Fox posted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409347 Title: "Enable horizontal scrolling" doesn't work with "Reverse scroll direction" To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1409347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848144] Re: Screen reader isn't enabled on login screen or user session after installation
This bug was fixed in the package ubiquity - 20.04.2 --- ubiquity (20.04.2) focal; urgency=medium * Make sure the screen-reader-enabled setting gets passed to the target system (LP: #1848144). -- Łukasz 'sil2100' Zemczak Fri, 29 Nov 2019 10:47:45 +0100 ** Changed in: ubiquity (Ubuntu) Status: In Progress => 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/1848144 Title: Screen reader isn't enabled on login screen or user session after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1848144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840741] Re: Notify-osd doesn't show icon with Gnotification
This bug was fixed in the package notify-osd - 0.9.35+20.04.20191129-0ubuntu1 --- notify-osd (0.9.35+20.04.20191129-0ubuntu1) focal; urgency=medium [ Khurshid Alam ] * Support 'image-path' as hint (LP: #1840741) -- Sebastien Bacher Fri, 29 Nov 2019 14:32:06 + ** Changed in: notify-osd (Ubuntu) Status: Confirmed => 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/1840741 Title: Notify-osd doesn't show icon with Gnotification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1840741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
** Attachment added: "kmod_bionic.c" https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1851553/+attachment/5308835/+files/kmod_bionic.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851553 Title: stress-ng-af-alg: bind failed, errno=110 (Connection timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1851553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
Attached synthetic reproducers used for Bionic (kmod_bionic.c) and Disco/Eoan (kmod.c) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851553 Title: stress-ng-af-alg: bind failed, errno=110 (Connection timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1851553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
Testing on Disco
$ lsb_release -cs
disco
$ uname -rv
5.0.0-36-generic #39-Ubuntu SMP Tue Nov 12 09:46:06 UTC 2019
Original: (ETIMEDOUT causes unsuccessful run)
$ dpkg -s stress-ng | grep Version:
Version: 0.09.57-0ubuntu3
$ stress-ng --af-alg 2 -t 120
stress-ng: info: [6902] dispatching hogs: 2 af-alg
stress-ng: info: [6902] successful run completed in 120.00s (2 mins, 0.00 secs)
$ sudo modprobe -r md4
$ sudo insmod kmod.ko
$ strace -e bind -o stress-ng_strace_bind.updates_kmod -f -- stress-ng --af-alg
2 -t 120
stress-ng: info: [2550] dispatching hogs: 2 af-alg
stress-ng: fail: [2552] stress-ng-af-alg: bind failed, errno=110 (Connection
timed out)
stress-ng: error: [2550] process 2552 (stress-ng-af-alg) terminated with an
error, exit status=1 (stress-ng core failure)
stress-ng: info: [2550] unsuccessful run completed in 120.00s (2 mins, 0.00
secs)
$ sudo rmmod kmod
$ grep -e ETIMEDOUT -e 'exited with' stress-ng_strace_bind.updates_kmod
2552 <... bind resumed> ) = -1 ETIMEDOUT (Connection timed out)
2552 +++ exited with 1 +++
2551 +++ exited with 0 +++
2550 +++ exited with 2 +++
[ 709.176027] hello
[ 732.529743] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '2552', (original) return value '10'
[ 732.530311] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '2551', (original) return value '10'
[ 732.533286] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '2552', (modified) return value '-62' (FIRST PID) return
address 'ac8c2a8f' -- ensure crypto_larval_lookup() calls
crypto_larval_add().
[ 732.536551] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '2551', sleep for 10 seconds (OTHER PID) -- wait FIRST
PID/crypto_larval_add()/down_write(_rwsem)
[ 732.545221] down_write(_alg_sem) in FIRST PID, FIRST CALL. sleep 15
seconds -- wait OTHER PID/__crypto_register_alg()
[ 742.773053] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '2551', slept for 10 seconds (OTHER PID)
[ 742.792739] crypto_alg_tested("md4-generic"), sleep 70 seconds. pid = 2556
-- expire the 60-second timeout of
FIRST_PID/crypto_larval_add()/crypto_larval_wait()
[ 747.637060] down_write(_alg_sem) in FIRST PID, FIRST CALL. slept 15
seconds
[ 814.453112] crypto_alg_tested("md4-generic"), slept 70 seconds
[ 814.630120] CPU feature 'AVX registers' is not supported.
[ 872.908469] bye
Modified: (ETIMEDOUT but still successful run)
$ sudo reboot
$ apt-cache madison stress-ng | grep ppa
stress-ng | 0.09.57-0ubuntu4 | http://ppa.launchpad.net/mfo/lp1851553/ubuntu
disco/main amd64 Packages
$ sudo apt install stress-ng
$ dpkg -s stress-ng | grep Version:
Version: 0.09.57-0ubuntu4
$ stress-ng --af-alg 2 -t 120
stress-ng: info: [973] dispatching hogs: 2 af-alg
stress-ng: info: [973] successful run completed in 118.84s (1 min, 58.84 secs)
$ sudo modprobe -r md4
$ sudo insmod kmod.ko
$ strace -e bind -o stress-ng_strace_bind.test-ppa_kmod -f -- stress-ng
--af-alg 2 -t 120
stress-ng: info: [1276] dispatching hogs: 2 af-alg
stress-ng: info: [1276] successful run completed in 120.00s (2 mins, 0.00 secs)
$ grep -e ETIMEDOUT -e 'exited with' stress-ng_strace_bind.test-ppa_kmod
1278 <... bind resumed> ) = -1 ETIMEDOUT (Connection timed out)
1277 +++ exited with 0 +++
1278 +++ exited with 0 +++
1276 +++ exited with 0 +++
Console:
[ 247.254557] hello
[ 250.850844] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1278', (original) return value '10'
[ 250.852201] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1277', (original) return value '10'
[ 250.854055] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1278', (modified) return value '-62' (FIRST PID) return
address 'b8ac2a8f' -- ensure crypto_larval_lookup() calls
crypto_larval_add().
[ 250.874032] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1277', sleep for 10 seconds (OTHER PID) -- wait FIRST
PID/crypto_larval_add()/down_write(_rwsem)
[ 250.887133] down_write(_alg_sem) in FIRST PID, FIRST CALL. sleep 15
seconds -- wait OTHER PID/__crypto_register_alg()
[ 261.090424] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1277', slept for 10 seconds (OTHER PID)
[ 261.118493] crypto_alg_tested("md4-generic"), sleep 70 seconds. pid = 1282
-- expire the 60-second timeout of
FIRST_PID/crypto_larval_add()/crypto_larval_wait()
[ 265.954373] down_write(_alg_sem) in FIRST PID, FIRST CALL. slept 15
seconds
[ 331.234630] crypto_alg_tested("md4-generic"), slept 70 seconds
[ 331.430396] CPU feature 'AVX registers' is not supported.
[ 331.481278] CPU feature 'AVX registers' is not supported.
[ 388.584495] bye
--
You
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
** Attachment added: "kmod.c" https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1851553/+attachment/5308836/+files/kmod.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851553 Title: stress-ng-af-alg: bind failed, errno=110 (Connection timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1851553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
** Attachment added: "kmod.c" https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1851553/+attachment/5308837/+files/kmod.c ** Description changed: [Impact] * Users running stress-ng's 'af-alg' stressor (which is part of the 'cpu' and 'os' classes of stressors) with 50+ instances, might get failure exit status and the message 'bind failed, errno=110 (Connection timed out)'. * For MAAS users, this means the CPU hardware tests (that run the 'cpu' class of stressors) on larger systems might report 'FAILED' status, thus possibly misleading admins about the hardware present in the system. * It has been determined the problem root cause is related to concurrent module loading request threshold in the kernel (50), which is exercised by the crypto API at the time of the bind() system call (so to load the crypto algorithm module requested). * The problem happens due to a race condition between the instance that exceeded the threshold of concurrent module loading (50 requests), then timed out while waiting for a second chance (5 seconds), and another instance that successfully made it and requested the module load but the module's self-tests didn't finish within the time-out running in the first instance (60 seconds), as all the CPUs are currently under stress; this error is then returned to userspace/bind(). * Not all instances fail with that error, as once the crypto algorithm module is successfully loaded (i.e., by another concurrent instance and the module self-tests eventually finished), the problem no longer occurs. * The fix simply checks for ETIMEDOUT errno/failure on the bind() system call, and performs a bounded retry loop (3 attempts), as the module may just have been loaded successfully by another instance. [Test Case] - * A synthetic reproducer is available; a kernel module that uses kprobes to -force the synchronization of af-alg instances to happen in the way needed -to reproduce the problem. + * A synthetic reproducer is available; a kernel module that uses kprobes to + force the synchronization of af-alg instances to happen in the way needed + to reproduce the problem. (comments #7 and #13, test in comments #10-#12) - * With the kernel module loaded, one of the af-alg instances (not all of -them) hits the bind() connection timed out if this patch is not applied. + * With the kernel module loaded, one of the af-alg instances (not all of + them) hits the bind() connection timed out if this patch is not applied. [Regression Potential] - * The code changes are minimal and contained within af-alg stressor + * The code changes are minimal and contained within af-alg stressor code. - * Differences in behavior might be af-alg/cpu/os stressors that now -pass/exit with successful status on larger systems. + * Differences in behavior might be af-alg/cpu/os stressors that now + pass/exit with successful status on larger systems. [Other Info] * Fix applied in stress-ng [1] on V0.10.09 and in Focal (development series). * Backport provided for these stable releases: Bionic, Disco, Eoan. [1] https://kernel.ubuntu.com/git/cking/stress- ng.git/commit/?id=637e0a9b7050cc69e76eeb7b61c14a659d8b8cfd [Original Description] The MAAS hardware test for CPU (long/12h) fails due to stress-ng-af-alg bind() errors. stress-ng-cpu-long <...> Failed [View log] disabled 'cpu-online' as it may hang the machine (enable it with the --pathological option) dispatching hogs: 72 af-alg, 72 atomic, 72 branch, 72 bsearch, 72 cache, 72 context, 72 cpu, 72 crypt, 72 fp-error, 72 funccall, 72 getrandom, 72 heapsort, 72 hsearch, 72 icache, 72 ioport, 72 lockbus, 72 longjmp, 72 lsearch, 72 malloc, 72 matrix, 72 membarrier, 72 memcpy, 72 mergesort, 72 nop, 72 numa, 72 opcode, 72 qsort, 72 radixsort, 72 rdrand, 72 str, 72 stream, 72 tree, 72 tsc, 72 tsearch, 72 vecmath, 72 wcs, 72 zlib stress-ng-numa: system has 2 of a maximum 1024 memory NUMA nodes stress-ng-stream: stressor loosely based on a variant of the STREAM benchmark code stress-ng-stream: do NOT submit any of these results to the STREAM benchmark results stress-ng-stream: Using CPU cache size of 25344K stress-ng-af-alg: bind failed, errno=110 (Connection timed out) stress-ng-af-alg: bind failed, errno=110 (Connection timed out) stress-ng-af-alg: bind failed, errno=110 (Connection timed out) stress-ng-af-alg: bind failed, errno=110 (Connection timed out) stress-ng-af-alg: bind failed, errno=110 (Connection timed out) stress-ng-af-alg: bind failed, errno=110 (Connection timed out) ... process 6626 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) process 6673 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) process 6713 (stress-ng-af_alg)
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
Testing on Eoan
===
$ lsb_release -cs
eoan
$ uname -rv
5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019
Original: (ETIMEDOUT causes unsuccessful run)
$ dpkg -s stress-ng | grep Version:
Version: 0.10.07-1ubuntu1
$ stress-ng --af-alg 2 -t 120
stress-ng: info: [9855] dispatching hogs: 2 af-alg
stress-ng: info: [9855] successful run completed in 120.00s (2 mins, 0.00 secs)
$ sudo modprobe -r md4
$ sudo insmod kmod.ko
$ strace -e bind -o stress-ng_strace_bind.updates_kmod -f -- stress-ng --af-alg
2 -t 120
stress-ng: info: [10875] dispatching hogs: 2 af-alg
stress-ng: fail: [10877] stress-ng-af-alg: bind failed, errno=110 (Connection
timed out)
stress-ng: error: [10875] process 10877 (stress-ng-af-alg) terminated with an
error, exit status=1 (stress-ng core failure)
stress-ng: info: [10875] unsuccessful run completed in 120.00s (2 mins, 0.00
secs)
$ sudo rmmod kmod
$ grep -e ETIMEDOUT -e 'exited with' stress-ng_strace_bind.updates_kmod
10877 <... bind resumed> ) = -1 ETIMEDOUT (Connection timed out)
10877 +++ exited with 1 +++
10876 +++ exited with 0 +++
10875 +++ exited with 2 +++
Console:
[ 6743.872738] hello
[ 6750.849145] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '10877', (original) return value '10'
[ 6750.850112] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '10876', (original) return value '10'
[ 6750.856261] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '10877', (modified) return value '-62' (FIRST PID)
return address '892c6f5a' -- ensure crypto_larval_lookup() calls
crypto_larval_add().
[ 6750.859332] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '10876', sleep for 10 seconds (OTHER PID) -- wait FIRST
PID/crypto_larval_add()/down_write(_rwsem)
[ 6750.870830] down_write(_alg_sem) in FIRST PID, FIRST CALL. sleep 15
seconds -- wait OTHER PID/__crypto_register_alg()
[ 6760.875908] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '10876', slept for 10 seconds (OTHER PID)
[ 6760.891766] crypto_alg_tested("md4-generic"), sleep 70 seconds. pid = 10881
-- expire the 60-second timeout of
FIRST_PID/crypto_larval_add()/crypto_larval_wait()
[ 6765.995913] down_write(_alg_sem) in FIRST PID, FIRST CALL. slept 15
seconds
[ 6831.531954] crypto_alg_tested("md4-generic"), slept 70 seconds
[ 6831.705902] CPU feature 'AVX registers' is not supported.
[ 6875.780559] bye
Modified: (ETIMEDOUT but still successful run)
$ sudo reboot
$ apt-cache madison stress-ng | grep ppa
stress-ng | 0.10.07-1ubuntu2 | http://ppa.launchpad.net/mfo/lp1851553/ubuntu
eoan/main amd64 Packages
$ sudo apt install stress-ng
$ dpkg -s stress-ng | grep Version:
Version: 0.10.07-1ubuntu2
$ stress-ng --af-alg 2 -t 120
stress-ng: info: [974] dispatching hogs: 2 af-alg
stress-ng: info: [974] successful run completed in 118.81s (1 min, 58.81 secs)
$ sudo modprobe -r md4
$ sudo insmod kmod.ko
$ strace -e bind -o stress-ng_strace_bind.test-ppa_kmod -f -- stress-ng
--af-alg 2 -t 120
stress-ng: info: [1250] dispatching hogs: 2 af-alg
stress-ng: info: [1250] successful run completed in 120.00s (2 mins, 0.00 secs)
$ sudo rmmod kmod
$ grep -e ETIMEDOUT -e 'exited with' stress-ng_strace_bind.test-ppa_kmod
1252 <... bind resumed> ) = -1 ETIMEDOUT (Connection timed out)
1251 +++ exited with 0 +++
1252 +++ exited with 0 +++
1250 +++ exited with 0 +++
Console:
[ 178.423467] hello
[ 195.578735] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1252', (original) return value '10'
[ 195.578740] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1252', (modified) return value '-62' (FIRST PID) return
address '8d6c6f5a' -- ensure crypto_larval_lookup() calls
crypto_larval_add().
[ 195.579607] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1251', (original) return value '10'
[ 195.579609] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1251', sleep for 10 seconds (OTHER PID) -- wait FIRST
PID/crypto_larval_add()/down_write(_rwsem)
[ 195.582565] down_write(_alg_sem) in FIRST PID, FIRST CALL. sleep 15
seconds -- wait OTHER PID/__crypto_register_alg()
[ 205.754961] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '1251', slept for 10 seconds (OTHER PID)
[ 205.764738] crypto_alg_tested("md4-generic"), sleep 70 seconds. pid = 1331
-- expire the 60-second timeout of
FIRST_PID/crypto_larval_add()/crypto_larval_wait()
[ 210.618994] down_write(_alg_sem) in FIRST PID, FIRST CALL. slept 15
seconds
$ [ 275.899046] crypto_alg_tested("md4-generic"), slept 70 seconds
[ 276.078957] CPU feature 'AVX registers' is not supported.
[ 403.156991] bye
** Attachment removed: "kmod.c"
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
Testing on Bionic
=
$ lsb_release -cs
bionic
$ uname -rv
4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019
Original: (ETIMEDOUT causes unsuccessful run)
$ dpkg -s stress-ng | grep Version:
Version: 0.09.25-1ubuntu4
$ stress-ng --af-alg 2 -t 120
$ sudo modprobe -r md4
$ sudo insmod kmod.ko
$ strace -e bind -o stress-ng_strace_bind.updates_kmod -f -- stress-ng --af-alg
2 -t 120
stress-ng: info: [24185] dispatching hogs: 2 af-alg
stress-ng: fail: [24187] stress-ng-af-alg: bind failed, errno=110 (Connection
timed out)
stress-ng: error: [24185] process 24187 (stress-ng-af_alg) terminated with an
error, exit status=1 (stress-ng core failure)
stress-ng: info: [24185] unsuccessful run completed in 120.12s (2 mins, 0.12
secs)
$ sudo rmmod kmod
$ grep -e ETIMEDOUT -e 'exited with' stress-ng_strace_bind.updates_kmod
24187 <... bind resumed> ) = -1 ETIMEDOUT (Connection timed out)
24187 +++ exited with 1 +++
24186 +++ exited with 0 +++
24185 +++ exited with 2 +++
Console:
[ 1447.068493] hello
[ 1454.324451] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '24187', (original) return value '0'
[ 1454.329008] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '24186', (original) return value '0'
[ 1454.332156] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '24187', (modified) return value '-62' (FIRST PID) --
ensure crypto_larval_lookup() calls crypto_larval_add().
[ 1454.335468] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '24186', sleep for 10 seconds (OTHER PID) -- wait FIRST
PID/crypto_larval_add()/down_write(_rwsem)
[ 1454.344373] down_write(_alg_sem) in FIRST PID, FIRST CALL. sleep 15
seconds -- wait OTHER PID/__crypto_register_alg()
[ 1464.467346] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '24186', slept for 10 seconds (OTHER PID)
[ 1464.485379] crypto_alg_tested("md4-generic"), sleep 70 seconds. pid = 24190
-- expire the 60-second timeout of
FIRST_PID/crypto_larval_add()/crypto_larval_wait()
[ 1469.587269] down_write(_alg_sem) in FIRST PID, FIRST CALL. slept 15
seconds
[ 1534.610212] crypto_alg_tested("md4-generic"), slept 70 seconds
[ 1534.788821] CPU feature 'AVX registers' is not supported.
[ 1616.714910] bye
Modified: (ETIMEDOUT but still successful run)
$ sudo reboot
$ apt-cache madison stress-ng | grep ppa
stress-ng | 0.09.25-1ubuntu5 | http://ppa.launchpad.net/mfo/lp1851553/ubuntu
bionic/main amd64 Packages
$ apt install stress-ng
$ dpkg -s stress-ng | grep Version:
Version: 0.09.25-1ubuntu5
$ stress-ng --af-alg 2 -t 120
$ sudo modprobe -r md4
$ sudo insmod kmod.ko
$ strace -e bind -o stress-ng_strace_bind.test-ppa_kmod -f -- stress-ng
--af-alg 2 -t 120
stress-ng: info: [5263] dispatching hogs: 2 af-alg
stress-ng: info: [5263] successful run completed in 120.15s (2 mins, 0.15 secs)
$ sudo rmmod kmod
$ grep -e ETIMEDOUT -e 'exited with' stress-ng_strace_bind.test-ppa_kmod
5265 <... bind resumed> ) = -1 ETIMEDOUT (Connection timed out)
5265 +++ exited with 0 +++
5264 +++ exited with 0 +++
5263 +++ exited with 0 +++
Console:
[ 181.908670] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '5265', (original) return value '0'
[ 181.913681] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '5264', (original) return value '0'
[ 181.915063] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '5265', (modified) return value '-62' (FIRST PID) --
ensure crypto_larval_lookup() calls crypto_larval_add().
[ 181.918165] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '5264', sleep for 10 seconds (OTHER PID) -- wait FIRST
PID/crypto_larval_add()/down_write(_rwsem)
[ 181.925744] down_write(_alg_sem) in FIRST PID, FIRST CALL. sleep 15
seconds -- wait OTHER PID/__crypto_register_alg()
[ 191.964132] security_kernel_module_request() module 'crypto-md4', comm
'stress-ng-af-al', pid '5264', slept for 10 seconds (OTHER PID)
[ 191.979817] crypto_alg_tested("md4-generic"), sleep 70 seconds. pid = 5269
-- expire the 60-second timeout of
FIRST_PID/crypto_larval_add()/crypto_larval_wait()
[ 197.084134] down_write(_alg_sem) in FIRST PID, FIRST CALL. slept 15
seconds
[ 263.132190] crypto_alg_tested("md4-generic"), slept 70 seconds
[ 263.342852] CPU feature 'AVX registers' is not supported.
[ 263.396340] CPU feature 'AVX registers' is not supported.
[ 395.333437] bye
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851553
Title:
stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
To manage notifications about this bug go to:
[Bug 1838691] Re: Can't create incremental backups when using python3 and newer Ceph versions.
Hi Chris, I've tried the fix in fedora/centos and Devstack environment and it fix the problem. Sadly, I don't have access to an instance with Ubuntu Cloud to try your package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838691 Title: Can't create incremental backups when using python3 and newer Ceph versions. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1838691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854480] Re: zfs_arc_max not working anymore in zfs 0.8.1
** Description changed: In the past I could limit the size of L1ARC by specifying "options zfs zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to - fill /sys/module/zfs/parameters/zfs_arc_max directly after login, but - none of those methods limits the size of L1ARC. It worked nicely in zfs - 0.7.x. + fill /sys/module/zfs/parameters/zfs_arc_max directly, but none of those + methods limits the size of L1ARC. It worked nicely in zfs 0.7.x. Nowadays I use a nvme drive with 3400 MB/s read throughput and I see not much difference between e.g booting the system from nvme and rebooting the system from L1ARC. Having a 96-99% hit rate for the L1ARC, I like to free up some memory, thus avoiding some delay of freeing memory from L1ARC while loading a VM. + + UPDATE: + + The system only limits the L1ARC, if we directly after the login write + the zfs_arc_max value to the file + /sys/module/zfs/parameters/zfs_arc_max. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zfsutils-linux 0.8.1-1ubuntu14.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 06:19:15 2019 InstallationDate: Installed on 2019-11-25 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Description changed: In the past I could limit the size of L1ARC by specifying "options zfs zfs_arc_max=3221225472" in /etc/modprobe.d/zfs.conf. I tried even to fill /sys/module/zfs/parameters/zfs_arc_max directly, but none of those methods limits the size of L1ARC. It worked nicely in zfs 0.7.x. Nowadays I use a nvme drive with 3400 MB/s read throughput and I see not much difference between e.g booting the system from nvme and rebooting the system from L1ARC. Having a 96-99% hit rate for the L1ARC, I like to free up some memory, thus avoiding some delay of freeing memory from L1ARC while loading a VM. + - UPDATE: The system only limits the L1ARC, if we directly after the login write the zfs_arc_max value to the file /sys/module/zfs/parameters/zfs_arc_max. + + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zfsutils-linux 0.8.1-1ubuntu14.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 06:19:15 2019 InstallationDate: Installed on 2019-11-25 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854480 Title: zfs_arc_max not working anymore in zfs 0.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852435] Re: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22
*** This bug is a duplicate of bug 1852586 *** https://bugs.launchpad.net/bugs/1852586 Hi, Andrej and Gianfranco. Thanks a lot for your help testing this. We were monitoring different reports about boot issues with 5.3.0-23, but we were not sure they were about the same issues. In fact, some of those reports were about linux-hwe-edge 5.3.0-23 that didn't have modules signed because of a difference in bionic tools, so we wanted to make sure before duplicating bugs to identify which ones were which. As the other one I marked this bug as a duplicate of (LP: #1852586) had the confirmation sent before (or so I noticed), I ended up submitting the fix to the mailing list with it as a buglink. So, this is now fix committed, and should land in -proposed by next week. Sorry for the troubles caused, and thanks again for all the help identifying and testing these reverts. Cascardo. ** This bug has been marked a duplicate of bug 1852586 Boot hangs after "Loading initial ramdisk ..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852435 Title: Boots fine with 5.3.0-19, doesn't boot any more with 5.3.0-22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997934]
Changing priority back to 'medium' since the number of duplicates is lower than 5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997934 Title: [Upstream] Spell checking doesn't warn users if the selected dictionary isn't installed, but rather returns a potentially incorrect result To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/997934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421575] Re: Desktop corruption when changing monitor config
** Changed in: xserver-xorg-video-intel Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #67 https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/67 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421575 Title: Desktop corruption when changing monitor config To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1421575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843729] Re: byobu ftbfs in eoan
Hi there, Byobu maintainer here. Nack, on the tab-to-whitespace changes. I'll have pep8 ignore E117. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1843729] Re: byobu ftbfs in eoan
Hi there, Byobu maintainer here. Nack, on the tab-to-whitespace changes. I'll have pep8 ignore E117. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421575]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/67. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421575 Title: Desktop corruption when changing monitor config To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1421575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854542] [NEW] Install of ubuntu 19.10 crashed during file copying with "faulty CD or HDD" although I installed from a good USB stick onto a good SSD
Public bug reported: - ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Fri Nov 29 23:17:20 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash nomodeset --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854542 Title: Install of ubuntu 19.10 crashed during file copying with "faulty CD or HDD" although I installed from a good USB stick onto a good SSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1854542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Hi, all. I'm afraid I'll need to reopen this bug. I was able to reproduce the issue on Bionic, using network-manager 1.10.6-2ubuntu1.2. However, when testing this on Eoan, using network- manager 1.20.4-2ubuntu2, I didn't reproduce the behaviour. The steps one takes to reproduce the issue, either on a s390 system or x86 (the issue is reproducible regardless of the platform) is: 1.) Create the bond interface with: nmcli conn add type bond con-name ifname ipv4.method disabled ipv6.method ignore 2.) Modify it to so set a manual IPv6 Address and auto-assign IPv4: nmcli c m bond.options " mode=active-backup, downdelay=0 , miimon=100 , updelay=0 , fail_over_mac=none , num_grat_arp=0 , primary_reselect=always " connection.interface-name ipv4.method auto ipv4.gateway "" ipv6.method manual 802-3-ethernet.mac-address "" ipv4.routes "" connection.id ipv6.never-default no ipv4.addresses "" ipv6.addresses 3.) Add the two slave ethernet devices, and change them with: nmcli c m connection.id connection .interface-name 802-3-ethernet.s390-subchannels 802-3-ethernet.s390-nettype qeth connection.autoconnect yes 802-3-ethernet.mac-address "" ipv4.method disabled ipv6.method ignore 802-3-ethernet.s390-options portno= ^ For repro steps on amd64 or ppc64, the s390-* parameters can be removed from the command. 4.) Add the two slave ethernet devices to the bond: nmcli c m 802-3-ethernet.mac-address "" connection.master connection.slave-type bond [ . . . ] You'll see that, on Bionic, the bond interface isn't assigned an IPv4 address. On Eoan, an IPv4 address is assigned as expected. I have reviewed network-manager's changelog [1], but I didn't find any smoking guns that could've solved the issue, hence the re-opening of the bug. Let me know if further evidence is needed to proceed. Thanks! [1] https://changelogs.ubuntu.com/changelogs/pool/main/n/network-manager /network-manager_1.20.4-2ubuntu2/changelog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854537] [NEW] When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running taks with the g
Public bug reported: When I ran "sudo update-grub" after changing the line in grub.conf to be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the windows would not appear. I was forced to open a tty session and reboot. Expected Results: The command runs but the screen does not turn black until I initiate a shutdown/reboot Actual Results: The screen turns black and the startup tasks and status appear over a black background, as it would when I push the up key when ubuntu starts up. This issue occurred at around 3:47 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 15:40:27 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro radeon.modeset=0 splash quiet vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854537 Title: When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running taks with the green "OK" letters next to them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854536] [NEW] When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running taks with the g
Public bug reported: When I ran "sudo update-grub" after changing the line in grub.conf to be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the windows would not appear. I was forced to open a tty session and reboot. Expected Results: The command runs but the screen does not turn black until I initiate a shutdown/reboot Actual Results: The screen turns black and the startup tasks and status appear over a black background, as it would when I push the up key when ubuntu starts up. This issue occurred at around 3:47 PM, EDT, on November 29, 2019. Description:Ubuntu 18.04.3 LTS Release:18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 15:45:03 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854536 Title: When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running taks with the green "OK" letters next to them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1854536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851961] Re: package wicd-daemon 1.7.4+tb2-6 failed to install/upgrade: installed wicd-daemon package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wicd (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/1851961 Title: package wicd-daemon 1.7.4+tb2-6 failed to install/upgrade: installed wicd-daemon package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wicd/+bug/1851961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853206] Re: All keyboard shortcuts do not work after a login
Hi, I have been using the fix for more than a week and I did not experienced the problem again. So it seems this is a proper fix for my problem Thanks a lot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853206 Title: All keyboard shortcuts do not work after a login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1853206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496542] Re: Running processes left after disabling screen reader
Howdy, also seeing speech-dispatcher running on 19.10. Some anecdotal info is that I restarted and tried enabling and then disabling Screen Reader on the login screen and it hasn't appeared in my sessions today since, including a few more restarts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848211] Re: [SRU] valgrind fails to use debug symbols from glib/gtk
The apport failure is unrelated and is caused and tracked by LP: #1854237. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848211 Title: [SRU] valgrind fails to use debug symbols from glib/gtk To manage notifications about this bug go to: https://bugs.launchpad.net/valgrind/+bug/1848211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853383] Re: autopkgtest regression in test_add_proc_info
** Tags added: update-excuse update-excuse-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853383 Title: autopkgtest regression in test_add_proc_info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1853383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
** Changed in: linux Status: In Progress => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #272 https://gitlab.freedesktop.org/drm/intel/issues/272 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841700] Re: instance ingress bandwidth limiting doesn't works in ocata.
I have tested the different upgrade scenarios outlayed on the spreadsheet linked to this case. I found an error with existing qos policies when upgrading from pike to ocata-patched which might require a further change on the patchset. I will mark this verification as failed and re-submit a new patch with the required bits. The results with all other combinations are shared next. Bundle deployed: http://paste.ubuntu.com/p/tMNX577zCk/ Steps executed: juju config neutron-api enable-qos=true ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack network qos policy create bw-limit +-+--+ | Field | Value| +-+--+ | description | | | id | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | | is_default | None | | name| bw-limit | | project_id | 2c16c3a423444a43a39e11fcc768ad22 | | rules | [] | | shared | False| +-+--+ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --max-burst-kbits 300 --ingress bw-limit ++--+ | Field | Value| ++--+ | direction | ingress | | id | eda4481f-61d0-4f52-91f7-fe979f776705 | | max_burst_kbps | 300 | | max_kbps | 300 | | name | None | | project_id | | ++--+ openstack network qos rule list bw-limit +--+--+-+--+-+--+---+---+ | ID | QoS Policy ID| Type| Max Kbps | Max Burst Kbits | Min Kbps | DSCP mark | Direction | +--+--+-+--+-+--+---+---+ | eda4481f-61d0-4f52-91f7-fe979f776705 | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | bandwidth_limit | 300 | 300 | | | ingress | +--+--+-+--+-+--+-- ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port list -f value | grep 10.5.150.5 7c010ca8-1e96-4419-a4e9-4c56da05c806 fa:16:3e:a1:38:50 ip_address='10.5.150.5', subnet_id='5bb6de3b-6c72-4ef5-a0c2-821dfafaa822' N/A ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port list -f value | grep 10.5.150.0 8c44909b-a4cf-4c7b-903f-f9f31f4a8045 fa:16:3e:4d:53:4e ip_address='10.5.150.0', subnet_id='5bb6de3b-6c72-4ef5-a0c2-821dfafaa822' N/A ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port set 7c010ca8-1e96-4419-a4e9-4c56da05c806 --qos-policy 7e6d0652-6cd4 -4d5c-b58e-b7664c1c4587 ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ openstack port set 8c44909b-a4cf-4c7b-903f-f9f31f4a8045 --qos-policy 7e6d0652-6cd4 -4d5c-b58e-b7664c1c4587 ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ for port in $(openstack port list -f value -c ID); do openstack port show $port | grep qos; done | qos_policy_id | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | | qos_policy_id | 7e6d0652-6cd4-4d5c-b58e-b7664c1c4587 | Tempest run: http://paste.ubuntu.com/p/RPgrvvz25J/ Pre-patched version ubuntu@niedbalski-bastion:~/tempest$ openstack network qos policy show 30c09b4b-0c51-4679-99b9-23b62ba247d7 +-+--+ | Field | Value| +-+--+ | description | | | id | 30c09b4b-0c51-4679-99b9-23b62ba247d7 | | is_default | None | | name| bw-limit | | project_id | 2c16c3a423444a43a39e11fcc768ad22 | | rules | [] | | shared | False| +-+--+ 1 ubuntu@niedbalski-bastion:~/tempest$ openstack network qos rule create --type bandwidth-limit --max-kbps 300 --max-burst-kbits 300 30c09b4b-0c51-4679-99b9-23b62ba247d7 ++--+ | Field | Value
[Bug 1826125]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/272. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853863] Re: freeipa replica crashes near end of basic install
I didn't have a DNS setup, so that part remains untested. Also, Fedora/Redhat is still on opendnssec 1.4.x while Debian (and Ubuntu) moved to 2.x some years ago, things like that will still have bugs. Someone with a support contract (and probably more than one customer) should require freeipa support, doubt it will happen otherwise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757731] Re: Please port your package away from Qt 4
** Changed in: libdrumstick (Ubuntu) Status: New => 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/1757731 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrumstick/+bug/1757731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 749443] Re: LAME 3.98.4 wrong tagged as 3.98.2 | Meerkat 64bit
This issue has been fixed. ** Changed in: lame (Ubuntu) Status: New => 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/749443 Title: LAME 3.98.4 wrong tagged as 3.98.2 | Meerkat 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/749443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852785] Re: ubuntu 18.04.3 : intel 7260 bluetooth firmware doesn't have working hsp/hfp profile
I confirm that the package fix the bug. I downloaded it from : https://launchpad.net/ubuntu/+source/linux-firmware/1.173.13/+build/18178805/+files/linux-firmware_1.173.13_all.deb I believe it may be necessary to halt, wait some seconds then start the computer after install (and not just restart the computer) as the firmware is loaded directly in the bluetooth adapter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852785 Title: ubuntu 18.04.3 : intel 7260 bluetooth firmware doesn't have working hsp/hfp profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851653] Re: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3
copy_file_range changed behavior on 5.3, which would cause such failures. LTP changes to accomodate that were committed on September 30th and October 29th, though. Maybe this could be caused by the combination of linux 5.3, glibc 2.27 and whatever ltp version was used. Do we track the ltp commit id that was tested somehow? Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851653 Title: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854530] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854530 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1854530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854530] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1
** 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/1854530 Title: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/1854530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
New Report: 1854534 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854534] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "xrandr from when I run xorg instead of wayland (despite the bug being for wayland)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+attachment/5308809/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854534 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851910] Re: Display does not show up (short flashes)
** Description changed: This issue started recently (I think it could be related to some package update. Steps to reproduce: - Power the PC on; - BIOS Boot screen (not visible, the display is off); - GRUB screen (not visible, the display is off); - Gnome Login screen (not visible, the display is off). Workaround: - - after a reasonable time for the Gnome Login Screen to be reached, inserting my user password starts the desktop session. Screen is never shown on first try (the best is to see short flashes of the desktop in the screen). The display keeps on trying to start. - - long press the power button to force power down and immedeately switch the PC back on --> after 1 or more workaround cycles the screen is shown (sometimes with wrong horizontal placement). + - after a reasonable time for the Gnome Login Screen to be reached, inserting my user password starts the desktop session. Screen is never shown on first try (the best I can get are short flashes of the desktop in the screen). The display keeps on trying to start. + - long press the power button to force power down and immediately switch the PC back on --> after 1 or more workaround cycles the screen is shown (sometimes with wrong horizontal placement). After the display is working, it works smoothly until the next power down (i.e. if I reboot the PC everything is visible from the BIOS Boot screen onward. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,decor,regex,compiztoolbox,move,resize,imgpng,place,animation,expo,grid,vpswitch,mousepoll,workarounds,snap,gnomecompat,unitymtgrabhandles,session,ezoom,wall,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 09:20:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 4.15.0-39-generic, x86_64: installed nvidia, 430.50, 4.15.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8613] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=0c1fbe60-f395-4935-a4dc-eaea4ee92682 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851910 Title: Display does not show up (short flashes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851910/+subscriptions
[Bug 1854534] [NEW] [radeon] Wayland sessions including the login screen are just static noise
Public bug reported: Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and disabling Wayland via editing GDM's custom.conf file. Description:Ubuntu 18.04.3 LTS Release:18.04 xwayland: Installed: 2:1.19.6-1ubuntu4.3 Candidate: 2:1.19.6-1ubuntu4.3 Version table: *** 2:1.19.6-1ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.19.6-1ubuntu4.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 13:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854534 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854534] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+attachment/5308810/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854534 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1298416] Re: inkscape crashed with SIGSEGV in g_datalist_get_data()
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298416 Title: inkscape crashed with SIGSEGV in g_datalist_get_data() To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1298416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216167] Re: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216167 Title: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers() To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1216167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1044064] Re: inkscape freezes in 12.10 after clicking on fonts button (see the picture)
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044064 Title: inkscape freezes in 12.10 after clicking on fonts button (see the picture) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1044064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986816] Re: Inkscape crashed with SIGSEGV when saving drawing for first time
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986816 Title: Inkscape crashed with SIGSEGV when saving drawing for first time To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/986816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275164] Re: inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275164 Title: inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color() To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1275164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308798/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633935] Re: Inkscape freezes when selecting font
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633935 Title: Inkscape freezes when selecting font To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1633935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308797/+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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
apport information ** Description changed: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: mutter + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-70-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308796/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853863] Re: freeipa replica crashes near end of basic install
Using the ppa, the upgrade to the primary server was successful. Then the replica install was successful, other than, at the end: ... Restarting named Updating DNS system records DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered SERVFAIL; Server ::1 UDP port 53 answered SERVFAIL DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered SERVFAIL; Server 127.0.0.1 UDP port 53 answered SERVFAIL unable to resolve host name registry1.1.quietfountain.com. to IP address, ipa-ca DNS record will be incomplete Global DNS configuration in LDAP server is empty You can use 'dnsconfig-mod' command to set global DNS options that would override settings in local named.conf files DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered SERVFAIL; Server 127.0.0.1 UDP port 53 answered SERVFAIL DNS query for registry1.1.quietfountain.com. 1 failed: All nameservers failed to answer the query registry1.1.quietfountain.com. IN A: Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered The DNS operation timed out.; Server 127.0.0.1 UDP port 53 answered The DNS operation timed out.; Server ::1 UDP port 53 answered SERVFAIL; Server 127.0.0.1 UDP port 53 answered SERVFAIL unable to resolve host name registry1.1.quietfountain.com. to IP address, ipa-ca DNS record will be incomplete WARNING: The CA service is only installed on one server (registry1.1.quietfountain.com). It is strongly recommended to install it on another server. Run ipa-ca-install(1) on another master to accomplish this. The ipa-replica-install command was successful ... The following ipa-ca-install proceeded without error. I suggest that as ubuntu has embraced ceph, it should consider, and for the same reasons, supporting freeipa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853863 Title: freeipa replica crashes near end of basic install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1853863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851553] Re: stress-ng-af-alg: bind failed, errno=110 (Connection timed out)
** Description changed: - Fix applied in stress-ng [1] on V0.10.09 and in Focal (development series), - working on the backport patch for the stable releases (Bionic, Disco, Eoan). + [Impact] - [1] https://kernel.ubuntu.com/git/cking/stress- + * Users running stress-ng's 'af-alg' stressor (which is part of the 'cpu' and + 'os' classes of stressors) with 50+ instances, might get failure exit status + and the message 'bind failed, errno=110 (Connection timed out)'. + + * For MAAS users, this means the CPU hardware tests (that run the 'cpu' class +of stressors) on larger systems might report 'FAILED' status, thus possibly +misleading administrators about the hardware present in the system. + + * It has been determined that the problem root cause is related to concurrent +module loading request threshold in the kernel (50), which is exercised by +the crypto API at the time of the bind() system call (so to load the crypto +algorithm module requested). + + * The problem happens due to a race condition between the instance that exceeded +the threshold of concurrent module loading (50 requests), then timed out while +waiting for a second chance (5 seconds), and another instance that successfully +made it and requested the module load but the module's self-tests didn't finish +within the time-out running in the first instance (60 seconds), as all the CPUs +are currently under stress; this error is then returned to userspace/bind(). + + * Not all instances fail with that error, as once the crypto algorithm module +is successfully loaded (i.e., by another concurrent instance and the module +self-tests eventually finished), the problem no longer occurs. + + * The fix simply checks for ETIMEDOUT errno/failure on the bind() system call, +and performs a bounded retry loop (3 attempts), as the module may just have +been loaded successfully by another instance. + + [Test Case] + + * A synthetic reproducer is available; a kernel module that uses kprobes to +force the synchronization of af-alg instances to happen in the way needed +to reproduce the problem. + + * With the kernel module loaded, one of the af-alg instances (not all of them) +hits the bind() connection timed out error if this fix/patch is not applied. + + [Regression Potential] + + * The code changes are minimal and contained within the af-alg stressor + code. + + * Differences in behavior might be af-alg/cpu/os stressors that now pass/exit +with successful status on larger systems. + + [Other Info] + + * Fix applied in stress-ng [1] on V0.10.09 and in Focal (development + series). + + * Backport provided for these stable releases: Bionic, Disco, Eoan. + + [1] https://kernel.ubuntu.com/git/cking/stress- ng.git/commit/?id=637e0a9b7050cc69e76eeb7b61c14a659d8b8cfd + + [Original Description] + + The MAAS hardware test for CPU (long/12h) fails due to stress-ng-af-alg + bind() errors. + + stress-ng-cpu-long <...> Failed [View log] + + disabled 'cpu-online' as it may hang the machine (enable it with the --pathological option) + dispatching hogs: 72 af-alg, 72 atomic, 72 branch, 72 bsearch, 72 cache, 72 context, 72 cpu, 72 crypt, 72 fp-error, 72 funccall, 72 getrandom, 72 heapsort, 72 hsearch, 72 icache, 72 ioport, 72 lockbus, 72 longjmp, 72 lsearch, 72 malloc, 72 matrix, 72 membarrier, 72 memcpy, 72 mergesort, 72 nop, 72 numa, 72 opcode, 72 qsort, 72 radixsort, 72 rdrand, 72 str, 72 stream, 72 tree, 72 tsc, 72 tsearch, 72 vecmath, 72 wcs, 72 zlib + stress-ng-numa: system has 2 of a maximum 1024 memory NUMA nodes + stress-ng-stream: stressor loosely based on a variant of the STREAM benchmark code + stress-ng-stream: do NOT submit any of these results to the STREAM benchmark results + stress-ng-stream: Using CPU cache size of 25344K + stress-ng-af-alg: bind failed, errno=110 (Connection timed out) + stress-ng-af-alg: bind failed, errno=110 (Connection timed out) + stress-ng-af-alg: bind failed, errno=110 (Connection timed out) + stress-ng-af-alg: bind failed, errno=110 (Connection timed out) + stress-ng-af-alg: bind failed, errno=110 (Connection timed out) + stress-ng-af-alg: bind failed, errno=110 (Connection timed out) + ... + process 6626 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) + process 6673 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) + process 6713 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) + process 6751 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) + process 6800 (stress-ng-af_alg) terminated with an error, exit status=1 (stress-ng core failure) + ... + unsuccessful run completed in 44935.38s (12 hours, 28 mins, 55.38 secs) + ... ** Description changed: [Impact] - * Users running stress-ng's 'af-alg' stressor (which is part of the 'cpu' and - 'os' classes of
[Bug 1019147] Re: Inkscape high cpu usage
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019147 Title: Inkscape high cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1019147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430614] Re: Inkscape crashes when I'm working on it.
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430614 Title: Inkscape crashes when I'm working on it. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1430614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 169028] Re: delete in right-click menu works differently than Del
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/169028 Title: delete in right-click menu works differently than Del To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/169028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308787/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308786/+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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308791/+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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308793/+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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308792/+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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308795/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308789/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308790/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308788/+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/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308794/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335684] Re: SIGSEGV, when Ctrl-Shift-W (Swatches) & then close
** Tags added: bug-migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335684 Title: SIGSEGV, when Ctrl-Shift-W (Swatches) & then close To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1335684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
