[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Hi, I'm sorry, but I no longer have Intel hardware, so I can't test this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059807] Re: Power management settings on Ryzen 7 5800H are missing
The options that are missing to me are the options on the indicator- cpufreq (and on /sys, of course). Using the 6.5 kernel, the only available options are "Desempenho" (Performance) and "Economia de Energia" (Powersave) and they don't seem to work at all. Using the 5.15 kernel, there are more options and (via CLI) it's possible to enable/disable turbo. This power profiles daemon seem to work with 6.5 kernel, but in subtle way: when a high load starts, it waits for a bit before rising the CPU frequencies to 4,4 GHz when set to powersave. It works, but its impact is minimal compared to the ability of using cpufreq to be able to, for example, disable turbo and have a set frequency. ** Attachment added: "Image showing the options with indicator-cpufreq with 5.15 kernel" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+attachment/5763392/+files/Captura%20de%20tela_2024-04-10_12-21-11.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059807 Title: Power management settings on Ryzen 7 5800H are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059807] [NEW] Power management settings on Ryzen 7 5800H are missing
Public bug reported: After the update to kernel 6.5, cpufreq no longer has options to set most governors or frequencies. The only available options are powersave and performance, but changing between them seem to have no effect. Consequently, the CPU temperature is always high: while with the 6.2 kernel it would idle at under 50°C, now with 6.5 it's idling at 65°C. Under a load that, with the 6.2 kernel, would result in around 80°C on CPU and 70°C on motherboard, now with the 6.5 it results in 100°C on both CPU and motherboard (I barely can touch the laptop because it gets so hot). To be able to use my laptop properly, I'm having to choose the 6.2 kernel on boot time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Mar 29 15:54:34 2024 InstallationDate: Installed on 2017-06-13 (2480 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2019-12-22 (1558 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059807 Title: Power management settings on Ryzen 7 5800H are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057990] Re: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load
** Changed in: ubuntu-desktop-provision Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057990 Title: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2057990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057990] Re: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load
It doesn't look like the same, as on bug 2056160 it's stated there is a blank window. However, on my testing, there was no window at all until I manually opened it. I have uploaded a video showing the attempted install, that failed with what seems to be bug 2057989 again (can't find grub-pc). ** Attachment added: "Video showing an attempted install (20240322)" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057990/+attachment/5758463/+files/tentativa20240322.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057990 Title: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2057990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057990] Re: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load
** Attachment added: "Screenshot showing how the shortcut for the installer isn't trusted" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057990/+attachment/5756108/+files/Captura%20de%20tela_2024-03-14_23-59-15.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057990 Title: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057990] [NEW] On Xubuntu noble-daily (20240315) the welcome dialog doesn't load
Public bug reported: When testing "Install (no Network) in Xubuntu Desktop amd64 in Noble Daily" on a QEMU virtual machine, it was noticed the welcome dialog never started. I expected it would load as "maybe-ubiquity" was present in /proc/cmdline. The VM was started with: qemu-system-x86_64 -accel kvm -net none -hda xub2404Daily.img -cdrom noble-desktop-amd64.iso -cpu host -smp cores=4,threads=2 -m 4G -device qxl-vga,xres=1280,yres=720 -boot menu=on ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Attachment added: "The entire /var/log from the live system after trying to install" https://bugs.launchpad.net/bugs/2057990/+attachment/5756107/+files/varLogInstallerError.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057990 Title: On Xubuntu noble-daily (20240315) the welcome dialog doesn't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057989] [NEW] Unable to install noble-daily (20240315) because it can't find grub-pc
Public bug reported: When testing the "Install (no Network) in Xubuntu Desktop amd64 in Noble Daily" on a QEMU virtual machine started with the command: qemu-system-x86_64 -accel kvm -net none -hda xub2404Daily.img -cdrom noble-desktop-amd64.iso -cpu host -smp cores=4,threads=2 -m 4G -device qxl-vga,xres=1280,yres=720 -boot menu=on The install failed. I have attached the entire /var/log from the live system with the data. The most relevant log seems to be on the installer directory: Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', '--download-only', 'grub-pc'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Package grub-pc is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: grub-common E: Package 'grub-pc' has no installation candidate Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False) TIMED subp(['udevadm', 'settle']): 0.020 Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False) Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False) Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False) Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False) Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False) Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False) Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False) Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False) finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on target system: ['grub-pc'] ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Attachment added: "The entire /var/log from the live system after the error" https://bugs.launchpad.net/bugs/2057989/+attachment/5756106/+files/varLogInstallerError.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057989 Title: Unable to install noble-daily (20240315) because it can't find grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973389] [NEW] Audio freezes, skips and failure to change volume when opening snap
Public bug reported: When opening a snap, sounds being played may start skipping or freezing and volume changes start failing, it can last from a few milliseconds to multiple seconds, depending on the program being opened and how the program playing the sound behaves. This was observed with Firefox, Chromium, Teams, Retroarch and Thunderbird snaps, at least. When opening them, it's possible to see at least 50% iowait on top, htop shows D for some processes, even pipewire, pipewire-pulse and wireplumber may iowait. A way to recreate this is to have some other program playing audio, as celluloid, and then open a snap or many of them at once for the first time. This computer has a 5400 RPM HDD, which surely is part of the problem, but still, sound freezes when opening the default web browser cause a very negative experience. I can't reproduce this opening a program installed as a deb, such as Stellarium, Google Chrome, SuperTuxKart or even Steam. I don't remember pulseaudio being so sensitive to iowait. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pipewire 0.3.48-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri May 13 22:08:16 2022 InstallationDate: Installed on 2017-06-13 (1795 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pipewire UpgradeStatus: Upgraded to jammy on 2019-12-22 (873 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973389 Title: Audio freezes, skips and failure to change volume when opening snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1973389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
On my computer I use the workaround of changing the Xorg session from modesetting to intel. To do this, firstly checking if xserver-xorg- video-intel is installed and then I create the file /etc/X11/xorg.conf.d/99-intel.conf with the following content: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "DRI""3" EndSection Then I restart the display manager to apply the change. Not only this crash stops happening to me, but it also solves another bug I face with default Xubuntu 20.04 settings: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870250 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
For now (1 hour and 40 minutes running glxgears in one screen), the system hasn't crashed. With the following command line: BOOT_IMAGE=/boot/vmlinuz-5.4.30+ root=UUID=6b4ae5c0-c78c-49a6-a1ba- 029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_fbc=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 cgroup_enable=memory swapaccount=1 The crash hasn't happened, but the Atomic update failure messages are still present and happening relatively often. Strange how the kernel from command 34 was fine until i915.enable_fbc=0 was set. By the way, does the bisect from the duplicate make sense? I found the result strange, but it seemed to fix it to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
Setting that option made my computer crash again. It crashed after 8 minutes of usage. ** Attachment added: "Syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+attachment/5361909/+files/logtt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
I tested the kernel from comment 34 and my computer is no longer crashing. With this kernel, it is possible to use default Xubuntu, without changing Xorg session or xfwm4 vblank_mode. What I noticed is that there are 1330 dmesg errors like: [52999.965468] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=3180783 end=3180784) time 440 us, min 763, max 767, scanline start 748, end 769 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
I did a bisect for this bug, now it is weekend and I was able to do tests on this computer. The bisect result is: 51d69817519f5f00041a1a039277f0367d76c82c is the first new commit commit 51d69817519f5f00041a1a039277f0367d76c82c Merge: 0174cb6ce944 f3efc406d67e Author: Linus Torvalds Date: Wed Jan 15 11:30:50 2020 -0800 Merge tag 'platform-drivers-x86-v5.5-3' of git://git.infradead.org/linux-platform-drivers-x86 Pull x86 platform driver fixes from Andy Shevchenko: - Fix keyboard brightness control for ASUS laptops - Better handling parameters of GPD pocket fan module to avoid thermal shock - Add IDs to PMC platform driver to support Intel Comet Lake - Fix potential dead lock in Mellanox TM FIFO driver and ABI documentation * tag 'platform-drivers-x86-v5.5-3' of git://git.infradead.org/linux-platform-drivers-x86: Documentation/ABI: Add missed attribute for mlxreg-io sysfs interfaces Documentation/ABI: Fix documentation inconsistency for mlxreg-io sysfs interfaces platform/x86: asus-wmi: Fix keyboard brightness cannot be set to 0 platform/x86: intel_pmc_core: update Comet Lake platform driver platform/x86: GPD pocket fan: Allow somewhat lower/higher temperature limits platform/x86: GPD pocket fan: Use default values when wrong modparams are given platform/mellanox: fix potential deadlock in the tmfifo driver platform/x86: intel-ips: Use the correct style for SPDX License Identifier Documentation/ABI/stable/sysfs-driver-mlxreg-io | 13 ++-- drivers/platform/mellanox/mlxbf-tmfifo.c| 19 - drivers/platform/x86/asus-wmi.c | 8 +--- drivers/platform/x86/gpd-pocket-fan.c | 27 ++--- drivers/platform/x86/intel_ips.h| 2 +- drivers/platform/x86/intel_pmc_core.h | 2 +- drivers/platform/x86/intel_pmc_core_pltdrv.c| 2 ++ 7 files changed, 46 insertions(+), 27 deletions(-) Which is unexpected to me, as it seems there is nothing related to i915. However, the computer really doesn't crash after this commit. The bisect log is below. Some of the kernels crash my computer in seconds: $ git bisect log git bisect start # old: [219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4 git bisect old 219d54332a09e8d8741c1e1982f5eae56099de85 # new: [d5226fa6dbae0569ee43ecfc08bdcd6770fc4755] Linux 5.5 git bisect new d5226fa6dbae0569ee43ecfc08bdcd6770fc4755 # old: [8c39f71ee2019e77ee14f88b1321b2348db51820] Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net git bisect old 8c39f71ee2019e77ee14f88b1321b2348db51820 # old: [76bb8b05960c3d1668e6bee7624ed886cbd135ba] Merge tag 'kbuild-v5.5' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild git bisect old 76bb8b05960c3d1668e6bee7624ed886cbd135ba # old: [018e0e3594f7dcd029d258e368c485e742fa9cdb] habanalabs: rate limit error msg on waiting for CS git bisect old 018e0e3594f7dcd029d258e368c485e742fa9cdb # old: [ec34c0157580a68c10dccbdd18c7701f0b317172] Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf git bisect old ec34c0157580a68c10dccbdd18c7701f0b317172 # new: [51d69817519f5f00041a1a039277f0367d76c82c] Merge tag 'platform-drivers-x86-v5.5-3' of git://git.infradead.org/linux-platform-drivers-x86 git bisect new 51d69817519f5f00041a1a039277f0367d76c82c # old: [b07f636fca1c8fbba124b0082487c0b3890a0e0c] Merge tag 'tpmdd-next-20200108' of git://git.infradead.org/users/jjs/linux-tpmdd git bisect old b07f636fca1c8fbba124b0082487c0b3890a0e0c # old: [658e1af5eec6d51f95fa81e61f67d2fe1c6376aa] Merge tag 'thermal-v5.5-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux git bisect old 658e1af5eec6d51f95fa81e61f67d2fe1c6376aa # old: [213356fe986faff3580f2c12c14773f53da32768] Merge tag 'usb-5.5-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb git bisect old 213356fe986faff3580f2c12c14773f53da32768 # old: [2fe20210fc5f5e62644678b8f927c49f2c6f42a7] mm: memcg/slab: call flush_memcg_workqueue() only if memcg workqueue is valid git bisect old 2fe20210fc5f5e62644678b8f927c49f2c6f42a7 # old: [452424cdcbcaf6a2ebaae4301da5a4e1850a941a] Merge branch 'parisc-5.5-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux git bisect old 452424cdcbcaf6a2ebaae4301da5a4e1850a941a # old: [0174cb6ce9449ce9b59cb9c6f4f64dc4df3de458] Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 git bisect old 0174cb6ce9449ce9b59cb9c6f4f64dc4df3de458 # old: [1f27dbd8265dbb379926c8f6a4453fe7fe26d7a3] platform/x86: GPD pocket fan: Allow somewhat lower/higher temperature limits git bisect old 1f27dbd8265dbb379926c8f6a4453fe7fe26d7a3 # old: [176a7fca81c5090a7240664e3002c106d296bf31] platform/x86: asus-wmi: Fix keyboard brightness cannot be set to 0 git bisect old 176a7fca81c5090a7240664e3002c106d296bf31 # old: [f3efc406d67e6236b513c4302133b0c9be74fd99]
[Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
The crash is still present with 5.4.0-24. The attached file has syslog, Xorg.0.log and xsession-errors. I noticed there are two workarounds for this: 1) Set the intel Xorg session instead of modesetting; 2) Change vblank_mode parameter from xfwm4: auto or glx will trigger this crash, xpresent or off won't. ** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870265/+attachment/5356465/+files/logs.tar.zst ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870641] Re: xfsettingsd doesn't open on login, making the system look ugly
I tested the live media with sha256sum 009c846c5596d7b4454a7b8eb7ca804a53dd7c58abf2e438da68e91018958133 and I still observed this problem. It's important to note that, if I run xfsettingsd after the live session starts, it starts fine. The problem is when the live session starts (after Ubiquity opens and choosing "Try Ubuntu"). Starting xfsettingsd later from the terminal or whisker menu works fine. It's only on live startup after Ubiquity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870641 Title: xfsettingsd doesn't open on login, making the system look ugly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1870641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
I'm not sure this is good or bad news, but glxgears also crashes the system: Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436043] BUG: kernel NULL pointer dereference, address: 0040 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436055] #PF: supervisor read access in kernel mode Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436056] #PF: error_code(0x) - not-present page Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436058] PGD 0 P4D 0 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436064] Oops: [#1] SMP PTI Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436070] CPU: 1 PID: 3240 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436072] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436211] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436216] Code: 00 48 c7 c6 a5 9e 95 c0 e8 af b7 8c f7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436218] RSP: 0018:9fee46a9f9c8 EFLAGS: 00010286 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436221] RAX: RBX: 93ae8eb42b40 RCX: Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436222] RDX: 93ae04cca800 RSI: 93ae8eb42b40 RDI: 0008 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436223] RBP: 9fee46a9f9e0 R08: 93ae24dd85a8 R09: 93ae24dd85a0 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436224] R10: 00014000 R11: 93ae3781bb00 R12: 93ae04cca800 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436226] R13: 0008 R14: 93ae04cca800 R15: 93ae24dd8480 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436228] FS: 7f0d25f6ca80() GS:93ae9e28() knlGS: Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436229] CS: 0010 DS: ES: CR0: 80050033 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436230] CR2: 0040 CR3: 0004e4e36004 CR4: 003606e0 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436232] DR0: DR1: DR2: Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436233] DR3: DR6: fffe0ff0 DR7: 0400 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436234] Call Trace: Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436361] i915_active_ref+0x24/0x200 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436465] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436555] eb_submit+0xff/0x440 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436631] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436643] ? sock_def_readable+0x40/0x70 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436648] ? __kmalloc_node+0x205/0x320 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436689] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436721] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436738] drm_ioctl_kernel+0xae/0xf0 [drm] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436753] drm_ioctl+0x234/0x3d0 [drm] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436805] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436817] ? vfs_writev+0xc3/0xf0 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436824] do_vfs_ioctl+0x407/0x670 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436832] ? fput+0x13/0x15 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436843] ? __sys_recvmsg+0x88/0xa0 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436854] ksys_ioctl+0x67/0x90 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436861] __x64_sys_ioctl+0x1a/0x20 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436872] do_syscall_64+0x57/0x190 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436882] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436889] RIP: 0033:0x7f0d26e8c37b Apr 8 15:13:49 Lenovo-ideapad-310-14ISK kernel: [ 3863.436896] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 Apr 8 15:13:49 Lenovo-ideapad-310-14ISK
[Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
Using the 5.6.3 kernel, this bug does not happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870939] [NEW] Micro tries to create log.txt on working directory every time it is opened
Public bug reported: Micro is creating a log.txt file on the working directory every time it is opened. Not only this creates an extra file, but this can cause micro to fail to open. For example: /etc/default$ micro grub 2020/04/05 12:47:49 error opening file: open log.txt: permission denied ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: micro 2.0.1-1 Uname: Linux 5.6.0+ x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 5 12:46:42 2020 InstallationDate: Installed on 2017-06-13 (1026 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: micro UpgradeStatus: Upgraded to focal on 2019-12-22 (104 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: micro (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870939 Title: Micro tries to create log.txt on working directory every time it is opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/micro/+bug/1870939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
I just tested the Xubuntu Beta ISO and, from it, I was able to reproduce the system crash. Unfortunately I was unable to obtain any logs, as sshd was no longer responsive and it was a live system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870641] Re: xfsettingsd doesn't open on login, making the system look ugly
** Attachment added: "systemd journal, with relevant messages" https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1870641/+attachment/5345923/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870641 Title: xfsettingsd doesn't open on login, making the system look ugly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1870641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870641] [NEW] xfsettingsd doesn't open on login, making the system look ugly
Public bug reported: When testing the Xubuntu Beta live media, it was observed xfsettingsd may fail to open. The consequence of this is that the appearance of Xubuntu is ugly. Many icons are missing and other have colors such way they are barely visible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-settings 4.14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: XFCE Date: Fri Apr 3 23:59:49 2020 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870641 Title: xfsettingsd doesn't open on login, making the system look ugly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1870641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870641] Re: xfsettingsd doesn't open on login, making the system look ugly
The attached image show the problems with the themes. Notice how the desktop icons are very hard to see. ** Attachment added: "Image" https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1870641/+attachment/5345922/+files/Captura%20de%20tela_2020-04-04_00-03-08.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870641 Title: xfsettingsd doesn't open on login, making the system look ugly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1870641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
This crash seems to be easy to reproduce. I made an Apitrace of the part of Gurumin with the scene that caused the first crash and let it replaying endlessly. After 1h30min, the system crashed again. The apitrace can be obtained from: https://mega.nz/file/8thHlYpa#_HBCUsIifUnD8R3K2U6v-- BWg8noez_Fn7KazWrrGRg A warning to those that want to play Gurumin: what was traced here can be considered mild spoilers. Log of the last crash: Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741100] BUG: kernel NULL pointer dereference, address: 0040 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741109] #PF: supervisor read access in kernel mode Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.74] #PF: error_code(0x) - not-present page Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741113] PGD 0 P4D 0 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741117] Oops: [#1] SMP PTI Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741123] CPU: 1 PID: 201976 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741125] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741208] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741213] Code: 00 48 c7 c6 a5 8e 5f c0 e8 af c7 82 f7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741214] RSP: 0018:b4fa4775f9c8 EFLAGS: 00010286 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741216] RAX: RBX: 93a6aeba7e40 RCX: Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741218] RDX: 93a4b6d2d900 RSI: 93a6aeba7e40 RDI: 0008 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741219] RBP: b4fa4775f9e0 R08: 93a72e958368 R09: 93a72e958360 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741220] R10: 93a4e7248280 R11: 0001 R12: 93a4b6d2d900 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741221] R13: 0008 R14: 93a4b6d2d900 R15: 93a72e958240 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741222] FS: 7f151279ba80() GS:93a7de28() knlGS: Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741224] CS: 0010 DS: ES: CR0: 80050033 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741225] CR2: 0040 CR3: 00027c8cc006 CR4: 003606e0 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741226] DR0: DR1: DR2: Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741227] DR3: DR6: fffe0ff0 DR7: 0400 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741229] Call Trace: Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741289] i915_active_ref+0x24/0x200 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741338] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741367] eb_submit+0xff/0x440 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741393] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741399] ? sock_def_readable+0x40/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741401] ? __kmalloc_node+0x205/0x320 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741428] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741453] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741466] drm_ioctl_kernel+0xae/0xf0 [drm] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741476] drm_ioctl+0x234/0x3d0 [drm] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741501] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741505] ? __switch_to_asm+0x40/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741506] ? __switch_to_asm+0x34/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741508] ? __switch_to_asm+0x40/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741509] ? __switch_to_asm+0x34/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741511] ? __switch_to_asm+0x40/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741512] ? __switch_to_asm+0x34/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741514] ? __switch_to_asm+0x40/0x70 Apr 3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741516] ? __switch_to+0x110/0x470 Apr 3 01:24:37
[Bug 1870265] [NEW] Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
Public bug reported: After playing Gurumin: A Monstrous Adventure for some time, the system crashed in an unrecoverable way. REISUB was required to get some logs. This crash happened with default Ubuntu's kernel, default Mesa and default Xorg session. I never observed a crash this serious using the intel Xorg driver. However, using the default (modesetting), the following unrecoverable crash happened after two hours: The syslog contains the following: Apr 2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php session files... Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: Succeeded. Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php session files. Apr 2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel NULL pointer dereference, address: 0040 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: supervisor read access in kernel mode Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: error_code(0x) - not-present page Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops: [#1] SMP PTI Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 200385 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 0018:bd8446f979c8 EFLAGS: 00010286 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: RBX: 9c477afaca80 RCX: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 9c4633bfc500 RSI: 9c477afaca80 RDI: 0008 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 00014000 R11: 9c47d1918b00 R12: 9c4633bfc500 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 0008 R14: 9c4633bfc500 R15: 9c47d6f4db00 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS: 7f99a3564a80() GS:9c47de28() knlGS: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS: 0010 DS: ES: CR0: 80050033 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 0040 CR3: 000556ca0001 CR4: 003606e0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: DR1: DR2: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: DR6: fffe0ff0 DR7: 0400 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477] i915_active_ref+0x24/0x200 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564] eb_submit+0xff/0x440 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615] ? sock_def_readable+0x40/0x70 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618] ? __kmalloc_node+0x205/0x320 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284742] drm_ioctl_kernel+0xae/0xf0 [drm] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284761] drm_ioctl+0x234/0x3d0 [drm] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284812] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284817] ? vfs_writev+0xc3/0xf0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284821] do_vfs_ioctl+0x407/0x670 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284824] ? fput+0x13/0x15 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284827] ?
[Bug 1870250] [NEW] Brightness control works in a inconsistent manner using modesetting
Public bug reported: When using the combination of modesetting Xorg driver with Intel GVT-g enabled, it was observed problems with brightness control. While the brightness control still has functionality, it works with significant delay for every change. Every change takes roughly half a second, making the change from zero to full brightness using the keyboard shortcuts take more than 10 seconds. The brightness keys are buffered too, making it hard to reach intermediate values. The attached video show the problem being reproduced using xfce4-power- manager notification on the xfce4-panel. This problem wasn't observed when using the Intel Xorg driver and this problem doesn't happen if modesetting is used without iGVT-g. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: CompositorRunning: None Date: Wed Apr 1 21:02:21 2020 DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2017-06-13 (1023 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: xorg-server UpgradeStatus: Upgraded to focal on 2019-12-22 (101 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870250 Title: Brightness control works in a inconsistent manner using modesetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870250] Re: Brightness control works in a inconsistent manner using modesetting
** Attachment added: "Video reproducing the problem using xfce4-power-manager" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870250/+attachment/5344513/+files/TEST002.mkv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870250 Title: Brightness control works in a inconsistent manner using modesetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868116] Re: QEMU monitor no longer works
Thank you for investigating this. I would bisect QEMU, but wouldn't investigate its libraries. Consequently, I would never find the cause of this problem. For now, I am using -monitor telnet:127.0.0.1:5,server,nowait to have access to the monitor on QEMU guests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868116] Re: QEMU monitor no longer works
** Summary changed: - QEMU console no longer works + QEMU monitor no longer works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1868116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868116] [NEW] QEMU console no longer works
Public bug reported: It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl- Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU console no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1868116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866982] [NEW] xfce4-screensaver is triggering a Xorg crash, backtrace suggests a xserver-xorg-video-intel problem
Public bug reported: xfce4-screensaver is triggering a Xorg crash. The bug report I did on xfce bugzilla against xfce4-screensaver is: https://bugzilla.xfce.org/show_bug.cgi?id=16528 The bug report there have the steps to reproduce, log files and the full backtrace of Xorg when the crash happened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1 Uname: Linux 5.6.0-050600rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: CompositorRunning: None CurrentDesktop: XFCE Date: Wed Mar 11 07:34:32 2020 DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2017-06-13 (1001 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0cf3:e360 Qualcomm Atheros Communications Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-050600rc4-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to focal on 2019-12-22 (79 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression reproducible ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866982 Title: xfce4-screensaver is triggering a Xorg crash, backtrace suggests a xserver-xorg-video-intel problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1866982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866732] [NEW] Unable to add policies on Chromium snap
Public bug reported: When using the Chromium snap, the policies located in the directory /etc /chromium-browser/policies/managed/ are no longer being read. The consequence is that the policies are not applied. This is particularly problematic on, for example, public computers, where browsing history and passwords may be saved, or on school computers, where the dinosaur game will be easily available. Is there another way I'm unaware of to add system-wide policies when using the Chromium snap? If not, would it be possible to make the snap read the settings in the /etc/chromium-browser/policies/managed/ directory? This would make the transition from deb to snap easier on systems which are already configured with system-wide policies. ** Affects: chromium-browser (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/1866732 Title: Unable to add policies on Chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
Good news! Using QEMU version 4.2.0 (Debian 1:4.2-3ubuntu1), I'm no longer able to reproduce this bug, key repeat is working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
Yes, disabling key repeat on xfce4-keyboard-settings in the host makes the problem stop happening. ** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
I was able to test on Mate and the same problem was observed: sticky keys with the right timing to release the keys. It also seems independent from the guest, even a Windows 10 guest was affected by this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861590] Re: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded
** Attachment added: "card0/error from Focal Daily Live ISO" https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+attachment/5324736/+files/card0errorfocallive.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861590 Title: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861590] Re: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded
As asked on #ubuntu+1 IRC, I tested on Xubuntu Focal Daily Live. It was needed 2 hours until I got a GPU hang, but once got it, the computer behaved exactly the same. ** Attachment added: "dmesg from Focal Daily Live ISO" https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+attachment/5324735/+files/dmesgfocallive.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861590 Title: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861590] [NEW] Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded
Public bug reported: It was noticed that, when using a heavy application, as a game, after some time GPU hangs will start to happen. They happen constantly and, if nothing is done, they never stop. The system is recoverable as the user can access a TTY and kill the offending application (after waiting a few minutes to start the TTY). After that, graphical demanding applications either run slower (it's not just the product of the lower frequency, it's different) or start causing the GPU hangs again. Restarting the applications that didn't cause GPU hangs will make them work normally again. This started to happen after the security fixes to Intel GPUs. Power management is also disabled. It was noticed drm-tip does not have this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 1 22:06:22 2020 InstallationDate: Installed on 2017-06-13 (963 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2019-12-22 (41 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: linux-signed-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861590 Title: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861590] Re: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded
** Attachment added: "card0/error" https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+attachment/5324715/+files/errorcrosscode54012.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861590 Title: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861590] Re: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+attachment/5324714/+files/dmesgcrosscode54012.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861590 Title: Intel GPU hangs constantly under load. After closing offending application, all GPU intensive programs run degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
I did some testing with the openbox session and noticed this problem isn't happening on it, even tried with onboard too. It happens on Xfce (both 4.12 an 4.14 were tested, as I was using Bionic before the upgrade). I would have to install other desktop environments to test, but I'm afraid one environment can cause problems in the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
To trigger this bug, I just write some text and then some key can get stuck. However, there is one reliable way to trigger this bug: hold the key for long enough it would be right before starting repeating the key on Mousepad (considering using Xubuntu ISO as the guest). If release with the right timing, that specific key will get stuck. The attached video shows the bug being triggered using onboard. ** Attachment added: "Video showing the problem" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+attachment/5320092/+files/qemubug000.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] [NEW] Sticky keys repeat indefinitely unless if pressed again
Public bug reported: It was noticed that, when using QEMU, keys pressed when using the guest can get stuck and repeat indefinitely. To undo that, the particular key has to be pressed again. While what is the key currently stuck can be obvious when it is a letter or number, Ctrl or even Enter can get stuck, which can lead to confirming doing dangerous actions in the guests (think replacing multiple files with a GUI file manager). A command as simple as: qemu-system-x86_64 -accel kvm -m 1536 -vga qxl -cdrom xubuntu-18.04.3 -desktop-amd64.iso Is triggering the bug. I tried using the workaround using -device usb- kbd but that didn't solve. It's currently being hard to use QEMU due to this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu-system-x86 1:4.0+dfsg-0ubuntu10 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jan 13 23:38:56 2020 InstallationDate: Installed on 2017-06-13 (944 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 0 0 33485 33480 22.7 qemu-system-x86_64 -accel kvm -m 1536 -cpu Skylake-Client -device nec-usb-xhci -device usb-host,id=cruzerblade,vendorid=0x0781,productid=0x5567 -bios /usr/share/ovmf/OVMF.fd -vga qxl -cdrom /home/usuario/Sistemas/xubuntu-18.04.3-desktop-amd64.iso -device usb-kbd kvm-nx-lpage-re S0 0 33490 2 0.0 [kvm-nx-lpage-re] kvm-pit/33485 S0 0 33494 2 0.0 [kvm-pit/33485] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (22 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859113] [NEW] No support for Zstandard
Public bug reported: As stated on https://facebook.github.io/zstd/ "Zstandard is a real-time compression algorithm, providing high compression ratios. It offers a very wide range of compression / speed trade-off, while being backed by a very fast decoder". Other Linux distributions even started to use the Zstandard in the place of xz compression for their packages due to how fast the decompression is, even if there is a small penalty on ratio. On my own testing, I noticed 17% faster compression and 88% faster decompression compared to xz while there was a 3% differences on compression ratio for system images. With this bug report, I ask to add support for Zstandard on at least file-roller. Currently, I have to use the command line tool zstd to work with files compressed using Zstandard. On Thunar, *.zst files appear as unknown and file-roller says there is no support for this file type. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.32.2-1 Uname: Linux 4.19.93-041969 x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jan 9 22:59:56 2020 InstallationDate: Installed on 2017-06-13 (940 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: file-roller UpgradeStatus: Upgraded to focal on 2019-12-22 (18 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859113 Title: No support for Zstandard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857810] [NEW] osspd no longer works: ERR: failed to connect context, state=5 (Bad state)
Public bug reported: After the upgrade to 20.04 daily, osspd no longer works. While the systemd service is starting, no program is being able to use it, giving warnings and errors when trying to use /dev/dsp. For the program that tried to play the sound, the following appears: /dev/dsp: Input/output error In the systemd logs of osspd, the following appears: dez 29 10:32:42 Lenovo-ideapad-310-14ISK osspd[23849]: ossp-padsp[usuario:23849] WARN: pa_context_subscribe() failed (Bad state) dez 29 10:32:42 Lenovo-ideapad-310-14ISK osspd[23849]: ossp-padsp[usuario:23849] WARN: failed to subscribe to context events (Bad state) dez 29 10:32:42 Lenovo-ideapad-310-14ISK osspd[23849]: ossp-padsp[usuario:23849] ERR: failed to connect context, state=5 (Bad state) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: osspd 1.3.2-11 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 29 10:29:47 2019 InstallationDate: Installed on 2017-06-13 (928 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: osspd UpgradeStatus: Upgraded to focal on 2019-12-22 (6 days ago) mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 ** Affects: osspd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857810 Title: osspd no longer works: ERR: failed to connect context, state=5 (Bad state) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osspd/+bug/1857810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852954] [NEW] After using iGVT-g guest and suspending system, GPU clock is locked at 100 MHz
Public bug reported: It was observed that after using an iGVT-g guest and suspending the system, the GPU clock is locked to 100 MHz on wake up. Normally, the GPU would idle at 300 MHz and go up to 1000 MHz when required, so the GPU starts operating at only 1/3 of the normal idle clock and 1/10 of the maximum clock. A kernel WARNING appears on wake up, being something like: [ 1492.886048] WARNING: CPU: 0 PID: 8653 at /build/linux-hwe-edge-ixgf89 /linux-hwe-edge-5.3.0/drivers/gpu/drm/i915/gem/i915_gem_pm.c:248 i915_gem_resume+0xc0/0xd0 [i915] The GPU is an Intel HD Graphics 520, the processor is an Intel Core i3-6100U. This bug is already fixed on drm-tip. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 17 21:49:28 2019 InstallationDate: Installed on 2017-06-13 (887 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (759 days ago) ** Affects: linux-signed-hwe-edge (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/1852954 Title: After using iGVT-g guest and suspending system, GPU clock is locked at 100 MHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1852954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852664] Re: Unable to boot 5.3.0-23, /dev/sda doesn't exist
Update: this bug only happens with the -lowlatency kernels. The -generic kernels are working correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852664 Title: Unable to boot 5.3.0-23, /dev/sda doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1852664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765775] Re: Window decoration becomes very large if the image has much more height than width
The following image is triggering the bug: https://i.imgur.com/To30M5D.png ** Changed in: eog (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765775 Title: Window decoration becomes very large if the image has much more height than width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1765775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852664] Re: Unable to boot 5.3.0-23, /dev/sda doesn't exist
On this computer no raid, lvm or md were configured, this is a normal desktop install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852664 Title: Unable to boot 5.3.0-23, /dev/sda doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1852664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852664] [NEW] Unable to boot 5.3.0-23, /dev/sda doesn't exist
Public bug reported: As proposed in #ubuntu IRC, I'm opening a bug using an older kernel version. The kernel 5.3.0-23 fails to boot, showing the following: https://i.imgur.com/PlcrAdQ.png There is no output from blkid and using ls /dev shows no /dev/sda. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-19-lowlatency 5.3.0-19.20~18.04.2+2 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-lowlatency 5.3.1 Uname: Linux 5.3.0-19-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 14 22:26:06 2019 InstallationDate: Installed on 2017-06-13 (884 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (756 days ago) ** Affects: linux-signed-hwe-edge (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/1852664 Title: Unable to boot 5.3.0-23, /dev/sda doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1852664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810105] Re: Hint showing volume never disappears, blocking buttons to minimize, maximize and close
I finally found a real computer on which this bug is present. The computer in question is a netbook manufactured by Positivo, the Mobo 5900, which is common on schools. It has a touchscreen with a pen which is compatible with evdev but that doesn't work with libinput. Its touchscreen is: Bus 004 Device 006: ID 22b9:0005 eTurboTouch Technology, Inc. The attached image not only shows the hint from the pulseaudio-plugin, but another one caused by pavucontrol. As a virtual keyboard is normally used because the netbook can be used as a tablet, the hints can make some keys impossible to use. ** Attachment added: "Captura de tela_2019-11-07_14-12-19.png" https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1810105/+attachment/5303552/+files/Captura%20de%20tela_2019-11-07_14-12-19.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810105 Title: Hint showing volume never disappears, blocking buttons to minimize, maximize and close To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1810105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850179] [NEW] GPU frequency greatly reduced after suspending, degrading performance significantly
Public bug reported: It was noticed that the GPU frequency is greatly reduced after waking up from suspension. Normally, the computer GPU's minimum frequency is 300 MHz and the maximum 1000 MHz. When this bug happens, the observed frequency is 100 MHz and multiple kernel WARNINGs appear. As the system uses Xfce and the screen resolution is 1366x768, for common desktop usage no problem is noticeable, but heavier tasks, as games, are greatly impacted. Steps to reproduce: 1) Have Intel GVT enabled (i915.enable_gvt=1); 2) Run a guest using Intel GVT-g. A guest command, for example: /usr/local/bin/qemu-system-x86_64 -name 'Windows 10' -nodefaults -M pc- i440fx-3.1,usb=true -machine kernel_irqchip=on -device qemu-xhci,id =qemu-xhci,addr=4,p2=15,p3=15 -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -hda redm.qcow2 -enable-kvm -cpu Skylake- Client,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_runtime -smp cores=2,threads=2 -m 3072M -bios /usr/local/share/qemu/bios.bin -device usb-tablet,id=tablet,bus=qemu-xhci.0,port=1 -vga none -monitor vc -serial stdio -display gtk,gl=on -device vfio- pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4-448a- 9f09-7b93adbf672c,x-igd- opregion=on,rombar=0,display=on,addr=0x3,id=iHD520 -netdev bridge,id=hostnet0,br=virbr0 -device e1000,netdev=hostnet0,id=net0,mac=aa:bb:cc:dd:ee:11,addr=0x8 -audiodev id=none,driver=none -device ivshmem-plain,memdev=HMB -object memory- backend-file,id=HMB,size=4M,mem-path=/dev/shm/test,share=on 3) Use the guest a bit and then turn off the guest; 4) Suspend the host system; 5) Wake up the host system; 6) Notice how GPU clock is limited to 100 MHz and heavier tasks are greatly degraded. Processor: Intel Core i3-6100U; Video: Intel HD Graphics 520; Architecture: amd64; RAM memory: 20 GB; Kernel version: 5.3.0-19-lowlatency; Distribution: Xubuntu 18.04.3 amd64. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-19-lowlatency 5.3.0-19.20~18.04.2+2 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-lowlatency 5.3.1 Uname: Linux 5.3.0-19-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Oct 28 13:06:25 2019 InstallationDate: Installed on 2017-06-13 (866 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (738 days ago) ** Affects: linux-signed-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850179 Title: GPU frequency greatly reduced after suspending, degrading performance significantly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1850179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757218] Re: QCA9377 isn't being recognized sometimes
I tested 4.15.0-55-generic and after multiple times turning the computer on and off, both Bluetooth and Wireless network were working correctly all the times. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830907] [NEW] Regression: QCA9377 randomly fails to connect on wake up and power on, kernel WARNING and 4WAY_HANDSHAKE_TIMEOUT
Public bug reported: In some situations, as waking up from suspend and sometimes on boot, the wireless network fails to connect. It attempts to connect endlessly but ultimately it fails. To make it work again, it's needed to remove the module ath10k_pci and add it again. On dmesg, it's noticeable there is a kernel WARNING and repeated messages of failure to connect with: deauthenticated from xx:xx:xx:xx:xx:xx (Reason: 15=4WAY_HANDSHAKE_TIMEOUT) The QCA9377 was working flawlessly with 4.18.0-17. Previous kernel versions failed to connect on a few specific networks which required removing the module as above. 4.18.0-20 fails to connect on many cases, has kernel WARNING and prints some additional warning messages on dmesg: [21910.162937] ath10k_pci :02:00.0: Unknown eventid: 118809 [21910.165810] ath10k_pci :02:00.0: Unknown eventid: 90118 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-lowlatency 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-lowlatency 4.18.20 Uname: Linux 4.18.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 29 10:50:23 2019 InstallationDate: Installed on 2017-06-13 (714 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2017-10-20 (586 days ago) ** Affects: linux-signed-hwe (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/1830907 Title: Regression: QCA9377 randomly fails to connect on wake up and power on, kernel WARNING and 4WAY_HANDSHAKE_TIMEOUT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1830907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830454] [NEW] Under memory pressure, graphics load may freeze the system
Public bug reported: When the system is under memory pressure (400 MB available from 8 GB and 600 MB swap usage), certain graphics workloads can freeze the system. Apparently, the system continues working, as sounds play normally. However, most programs seem to freeze, the screen no longer updates, nor the mouse moves, nor the keyboard lights from Num Lock, Caps Lock and Scroll Lock work. In the last crash I was playing Elite Dangerous using Steam Play with DXVK and was in a Discord call in Opera Developer. When the system froze, I was still able to talk and hear in the call and pressing Alt+PrintScreen+S allowed the disk to sync, as the hard disk could be heard and the syslog was saved. The pattern to have this is to be under memory pressure and have a heavy graphics workload. If the conditions are met, then this may happen. This is a rare event, but it seems to be impossible to recover when it happens as it seems to be impossible to remove the i915 module, even using the force options. Forcibly powering off by holding the power button is the only option. Distribution: Xubuntu 18.04.2 amd64; Kernel version: 4.18.0-20-lowlatency; Processor: Intel Core i3-6100U; Video: Intel HD Graphics 520; RAM: 8 GB. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-lowlatency 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-lowlatency 4.18.20 Uname: Linux 4.18.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 24 22:49:15 2019 InstallationDate: Installed on 2017-06-13 (710 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2017-10-20 (582 days ago) ** Affects: linux-signed-hwe (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/1830454 Title: Under memory pressure, graphics load may freeze the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1830454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805150] Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000000f0
The HWE kernel on Bionic does not have this problem anymore, as it was patched in a previous update. Previous kernel versions (as 4.15 and 4.17) seem to never hit this particular bug, but the kernel bugzilla discussion suggests the bug was present on older versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805150 Title: BUG: unable to handle kernel NULL pointer dereference at 00f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1805150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824175] [NEW] iGVT-g guest does not load graphics: kernel WARNING and wedged GPU
Public bug reported: On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel GVT-g guest, it was noticed that the graphical interface does not load. The following message appears: [ 19.844904] i915 :00:03.0: Failed to initialize GPU, declaring it wedged! And there are two kernel WARNING that appear. The first WARNING seems harmless and it was already reported: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is related to the host kernel, on this case 4.18.0-17 from HWE. The second WARNING is new and probably is related to the failure to load the graphics. It is possible to access the guest using the serial console. While the system claims GDM is working, there is no graphical interface visible. I have tested with Xubuntu 19.04 Disco Dingo Beta too and the same problem was noticed: two kernel WARNING, a wedged GPU and failure to load the graphics, even if the LightDM services was shown as running by systemctl status. Ubuntu 18.04 guests with kernel 4.15 and 4.18 are working. Mageia 7 guests with kernel 5.0.7 are working too, this seems related to the 5.0.0 kernel from Disco. Tested with both 5.0.0-7 and 5.0.0-8. Example of QEMU command line used: qemu-system-x86_64 -global PIIX4_PM.disable_s4=1 -M pc,usb=false -machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -name "Ubuntu Disco" -k pt-br -nodefaults -accel kvm -m 2G -cpu host -smp cores=2,threads=1 -netdev user,id=net0 -device e1000,netdev=net0,addr=8 -device vfio- pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/84de120a-c340-48fc- ba40-62f54c76f3ad,rombar=0,display=on,addr=0x3,id=iHD520 -device nec- usb-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 -device usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display gtk,gl=on -hda /home/usuario/.local/share/libvirt/images/ubuntu_disco.qcow2 -monitor vc -serial vc ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-8-generic 5.0.0-8.9 ProcVersionSignature: User Name 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Apr 10 12:04:47 2019 InstallationDate: Installed on 2019-04-09 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) IwConfig: ens8 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 002: ID 46f4:0002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=deb9f102-2eaf-4c05-96da-8c541c55726b ro quiet splash console=ttyS0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824175 Title: iGVT-g guest does not load graphics: kernel WARNING and wedged GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818249] [NEW] Panel screen does not turn on after login if notebook was suspended by closing the lid
Public bug reported: On Xubuntu 18.04, if it's set on power manager settings to suspend the notebook if the lid is closed, when it's open, the login screen appears but after the login the screen turns off. It was observed with xrandr that no resolution is set. To fix this, I have to do one of these three actions: 1) Use the xrandr command blindly; 2) Restart LightDM from a TTY; 3) Reboot. When suspending using the Whisker Menu or using systemctl suspend, the notebook panel turns on normally after login. It's happening only when suspending by closing the notebook lid. Maybe it detects no screen connected and then unset all resolutions? The notebook model page is: https://pcsupport.lenovo.com/br/pt/products /laptops-and-netbooks/300-series/310-14isk/80ug/80ugbr ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 1 12:24:33 2019 InstallationDate: Installed on 2017-06-13 (625 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2017-10-20 (497 days ago) ** Affects: lightdm (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/1818249 Title: Panel screen does not turn on after login if notebook was suspended by closing the lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1818249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814187] [NEW] package grub-efi-amd64 2.02-2ubuntu8.10 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127
Public bug reported: I used sudo apt update and sudo apt upgrade. 45 packages updated, 7 new installed (kernel). All kernels installed are from Ubuntu repositories, the system was upgraded a few times already. The kernels the system have: 4.15.0-45-generic 4.15.0-44-generic 4.15.0-43-generic 4.15.0-22-generic 4.10.0-26-generic 4.4.0-83-generic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.10 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 31 21:53:58 2019 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2017-07-24 (556 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=984701f6-117a-4fb5-ba8e-761744701fff ro quiet Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.8 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.10 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-04-27 (279 days ago) ** Affects: grub2 (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/1814187 Title: package grub-efi-amd64 2.02-2ubuntu8.10 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810108] Re: Failure to boot as QEMU guest when using -device virtio-vga, virgl=true
I can no longer reproduce this with newer Xubuntu Bionic Daily images, the guest is booting normally with 4.15.0-43. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810108 Title: Failure to boot as QEMU guest when using -device virtio-vga,virgl=true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810105] Re: Hint showing volume never disappears, blocking buttons to minimize, maximize and close
It seems that this happen only if using the QEMU -device virtio-tablet- pci It seems all other input devices make the hint disappear as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810105 Title: Hint showing volume never disappears, blocking buttons to minimize, maximize and close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1810105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810105] Re: Hint showing volume never disappears, blocking buttons to minimize, maximize and close
Yes, it happens with a new user. If I trigger this bug, returning to greeter with dm-tool switch-to- greeter, login with other user, use the other user account, log out, log in again to the first user, the hint is still visible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810105 Title: Hint showing volume never disappears, blocking buttons to minimize, maximize and close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1810105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810108] [NEW] Failure to boot as QEMU guest when using -device virtio-vga, virgl=true
Public bug reported: Installed Xubuntu 18.04 in a QEMU virtual machine using -device virtio- vga,virgl=true fails to boot. Even setting to output boot messages to a serial console no messages appear as if it never tried to boot at all. What makes this strange is that the live media works correctly using -device virtio-vga,virgl=true, but then, on reboot, the installed system fails to boot. To make the guest work it's required to remove the option ,virgl=true from the command line. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Sun Dec 30 17:33:21 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230) IwConfig: ens2 no wireless extensions. lono wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 virtiodrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU ** Affects: linux (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/1810108 Title: Failure to boot as QEMU guest when using -device virtio-vga,virgl=true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810107] [NEW] Crash on QEMU guest with virtio VGA if window is resized
*** This bug is a duplicate of bug 1665048 *** https://bugs.launchpad.net/bugs/1665048 Public bug reported: When using Xubuntu on QEMU with virtio VGA xfce4-display-settings crash if the QEMU window was resized. If using xrandr to adjust the resolution then xfce4-display-settings starts to work again. This is the backtrace: (gdb) bt #0 convert_xfce_output_info (output_id=) at main.c:1668 #1 0xc4a3 in get_output_for_window (window=) at main.c:2754 #2 select_current_output_from_dialog_position (app=0x55b6ba00) at main.c:2791 #3 dialog_map_event_cb (widget=, event=, data=0x55b6ba00) at main.c:2805 #4 0x7749d38b in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #5 0x766fb10d in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7670dbf1 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x767160af in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x7671712f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x775b32bc in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #10 0x7749bb03 in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #11 0x7711102c in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 #12 0x75931387 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x759315c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x759318d2 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7749aa37 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #16 0x555617e1 in display_settings_show_main_dialog (display=) at main.c:2899 #17 0xb465 in main (argc=, argv=) at main.c:3201 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-settings 4.12.4-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 30 17:23:54 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230) SourcePackage: xfce4-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-settings (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/1810107 Title: Crash on QEMU guest with virtio VGA if window is resized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1810107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810105] [NEW] Hint showing volume never disappears, blocking buttons to minimize, maximize and close
Public bug reported: When hovering the mouse over the volume indicator or changing its volume using the mouse wheel it shows the current volume set as a hint. For example: Volume 100% The problem is that the hint never disappears, not even clicking on it. On some occasions the hint can cover the minimize, maximize and close buttons, causing significant problems on using the desktop environment, as these three buttons won't be usable anymore with the hint over it. Where the hint appears it's no longer possible to interact with the screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-pulseaudio-plugin 0.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 30 17:09:23 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230) SourcePackage: xfce4-pulseaudio-plugin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-pulseaudio-plugin (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/1810105 Title: Hint showing volume never disappears, blocking buttons to minimize, maximize and close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-pulseaudio-plugin/+bug/1810105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809319] [NEW] Wallpapers are no longer switched if system is suspended or hibernated
Public bug reported: I configured xfdesktop to change wallpapers chronologically, the directory has 24 wallpapers so it changes the wallpaper once per hour and I noticed that if I suspend or hibernate the computer, when I wake it up the wallpaper is kept as the one from the moment it was suspended and it needs at least two transition times to work again. On my case it is two hours. To make the wallpaper change work immediately it's needed to terminate the xfdesktop process and start it again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfdesktop4 4.12.3-4ubuntu2 Uname: Linux 4.20.0-rc7-drm-tip-3ac901085a9fae8699716ac44579dab1dec546c3+ x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 20 18:21:40 2018 InstallationDate: Installed on 2017-06-13 (554 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: xfdesktop4 UpgradeStatus: Upgraded to bionic on 2017-10-20 (426 days ago) ** Affects: xfdesktop4 (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/1809319 Title: Wallpapers are no longer switched if system is suspended or hibernated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1809319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429030] Re: netboot mini.iso doesn't support UEFI boot
I tried Precise, Trusty, Bionic and Cosmic amd64 Mini ISOs and all of them are booting successfully in QEMU with OVMF. However, none of them are booting in a UEFI physical machine. It's strange this bug is present for three years: both Desktop and Server images have a functional bootloader. Those unused FAT12 partition take as much as 1/6 of the Mini image sizes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429030 Title: netboot mini.iso doesn't support UEFI boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1429030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
What causes this WARNING is the host kernel. Using latest drm-tip (d63c50f2b014037b43c1c0f108c61e0a31ede3c1) in the host, there is no WARNING in the guest, while the WARNING happens when the host uses 4.18.0-12 (HWE 18.04 Edge). 4.15.0-42 does not support iGVT-g with dma-buf, so it's not useful to test. It seems the results weren't dependent of the Linux kernel version on the guest: they were the same with 4.18.0-11, 4.18.0-12 and 4.19.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799102 Title: WARNING on boot in Intel GVT-g guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805150] [NEW] BUG: unable to handle kernel NULL pointer dereference at 00000000000000f0
Public bug reported: The bug reported https://bugzilla.kernel.org/show_bug.cgi?id=201377 is present in the kernel from hwe-18.04-edge in Bionic Beaver and seems to cause the same problems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-12-lowlatency 4.18.0-12.13~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-12.13~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-12-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Nov 26 12:01:32 2018 InstallationDate: Installed on 2017-06-13 (530 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (402 days ago) ** Affects: linux-signed-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805150 Title: BUG: unable to handle kernel NULL pointer dereference at 00f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1805150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804898] [NEW] System crashes hard after Intel GPU hang
Public bug reported: With any kernel starting from 4.18-rc1, if the system has an Intel GPU and suffers a GPU hang, the system will crash a bit later, mostly when another demanding tasks is started or finished. This crash or leaves nothing in the logs or ends corrupting the logs, making it nigh impossible to get relevant information about it. The crash was observed after GPU hangs caused by multiple applications, from web browsers to games using DXVK. The upstream bug is at https://bugs.freedesktop.org/show_bug.cgi?id=107945 While this bug is not new on upstream, soon Ubuntu Bionic Beaver will have 4.18 available, so I think it's relevant to report this here too. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-lowlatency-hwe-18.04-edge 4.18.0.12.61 ProcVersionSignature: Ubuntu 4.18.0-12.13~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-12-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Nov 23 20:55:28 2018 InstallationDate: Installed on 2017-06-13 (527 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-meta-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (399 days ago) ** Affects: linux-meta-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804898 Title: System crashes hard after Intel GPU hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-edge/+bug/1804898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
How should I test the Cosmic Cuttlefish proposed kernel? I don't want to upgrade my install, currently 18.04 LTS, to 18.10, which has only 9 months support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798165 Title: Vulkan applications cause permanent memory leak with Intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798165 Title: Vulkan applications cause permanent memory leak with Intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757218] Re: QCA9377 isn't being recognized sometimes
I shutdown and turned on the computer using this kernel four times and in none the problem happened. With the default Bionic kernel the failure on boot would have happened twice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
This happened to me when using Ubuntu Cosmic Cuttlefish with htop and tilix installed beyond the clean install. I was able to open the applications that are available in the dock and noticed the bar resizing when hovering over it. Later multiple graphical bugs started to happen and in the next boot Xorg was failing to start. Rebooting again solved the login issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766030] Re: CPU usage has a color with no description
Strange, to me 3.0.0beta5 is not fixed, it still has the color difference in virtualization load between the help and the meters. To be sure, I built 3.0.0beta5 both in Ubuntu 18.04 and CentOS 7 and in both the color discrepancy still exists in both systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766030 Title: CPU usage has a color with no description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/1766030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799102 Title: WARNING on boot in Intel GVT-g guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
dmesg with 4.19.0-041900-generic is attached. 4.19-rc8 has the same WARNING on boot. ** Attachment added: "dmesg with 4.19.0-041900-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+attachment/5204537/+files/dmesg ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799102 Title: WARNING on boot in Intel GVT-g guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799102] Re: WARNING on boot in Intel GVT-g guest
Host information: OS: Xubuntu 18.04.1 (amd64); Kernel: 4.17.19 with 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 applied to fix https://bugs.freedesktop.org/show_bug.cgi?id=107899; QEMU: 3.0.0; QEMU command line: env PULSE_LATENCY_MSEC=5 QEMU_AUDIO_ADC_VOICES=0 QEMU_AUDIO_DRV=pa qemu-system-x86_64 \ -name "Ubuntu Cosmic" -k pt-br -nodefaults -enable-kvm -cpu host -smp cores=2,threads=2 -m 2G \ -device vfio-pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/ef5f4cb6-734b-11e8-aaff-9fff2622012e,rombar=0,display=on,x-intx-mmap-timeout-ms=0x200,addr=0x3,id=iHD520 \ -device qemu-xhci,id=xhcihub -device usb-tablet,id=usbtablet -device usb-audio,id=usbaudio,buffer=6144 -bios /usr/share/ovmf/OVMF.fd \ -display gtk,gl=on -hda ubuntucosmic.qcow2 -monitor vc -serial mon:stdio \ -machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -M pc,usb=true \ -netdev user,id=net0,hostfwd=::5454-:22 -device e1000,netdev=net0,addr=8 ** Bug watch added: freedesktop.org Bugzilla #107899 https://bugs.freedesktop.org/show_bug.cgi?id=107899 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799102 Title: WARNING on boot in Intel GVT-g guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799102] [NEW] WARNING on boot in Intel GVT-g guest
Public bug reported: When booting Ubuntu Cosmic Cuttlefish 18.10 in an Intel GVT-g Virtual Machine, a kernel WARNING appears in dmesg, with the following: [3.563734] WARNING: CPU: 3 PID: 346 at drivers/gpu/drm/i915/i915_irq.c:161 gen3_assert_iir_is_zero+0x38/0xa0 [i915] I have not noticed negative effects in the VM, but a kernel WARNING probably has relevance. While I added a custom EDID to fix resolution, the WARNING happens without custom EDID set too. I will add information about the host in the next message. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1896 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 19:44:44 2018 InstallationDate: Installed on 2018-10-18 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. ens8 no wireless extensions. Lsusb: Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 46f4:0002 Bus 002 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=6cb7fc66-eb2c-4203-9d7d-2aa2665911ac ro quiet splash drm.edid_firmware=EDID_E1941.bin log_buf_len=16M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.0 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799102 Title: WARNING on boot in Intel GVT-g guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788727] Re: upgrade crashing due to unsigned kernels
Shouldn't this new Ubuntu bootloader refuse to boot unsigned kernels, is this refusal to boot not implemented yet or I understood its goal incorrectly? In the current state it seems to have no benefits, as I can boot any kernel I want from Ubuntu's bootloader, and cause a lot of trouble with the failing updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788727 Title: upgrade crashing due to unsigned kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
This kernel has the bug fixed. After one hour open, a game using DXVK did not allocate any memory it couldn't free when closed. It would leak around 600 MB in the same time previously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798165 Title: Vulkan applications cause permanent memory leak with Intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU
** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798165 Title: Vulkan applications cause permanent memory leak with Intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798165] [NEW] Vulkan applications cause permanent memory leak with Intel GPU
Public bug reported: Vulkan applications, as Dota 2 and DXVK games cause a memory leak where memory is never freed and can cause a system crash if the applications are used for long enough. Certain applications can make the leak be as high as 10 MB/minute. Details about this bug can be seen at https://github.com/doitsujin/dxvk/issues/632 and https://bugs.freedesktop.org/show_bug.cgi?id=107899 This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18. The particular commit is: commit a2cef7d049f07995406b403605119a54881daf15 Author: Jason Ekstrand Date: Wed Sep 26 02:17:03 2018 -0500 drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream. We attempt to get fences earlier in the hopes that everything will already have fences and no callbacks will be needed. If we do succeed in getting a fence, getting one a second time will result in a duplicate ref with no unref. This is causing memory leaks in Vulkan applications that create a lot of fences; playing for a few hours can, apparently, bring down the system. Cc: sta...@vger.kernel.org Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899 Reviewed-by: Chris Wilson Signed-off-by: Jason Ekstrand Signed-off-by: Sean Paul Link: https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com Signed-off-by: Greg Kroah-Hartman On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as: https://i.imgur.com/qMAvuwl.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario4655 F pulseaudio /dev/snd/seq:usuario4640 F timidity CurrentDesktop: XFCE Date: Tue Oct 16 14:16:54 2018 HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7 InstallationDate: Installed on 2017-06-13 (489 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt i915.enable_gvt=1 i915.fastboot=1 resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** Affects: linux (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/1798165 Title: Vulkan applications cause permanent memory leak with Intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797193] [NEW] xfdesktop assert failure: corrupted double-linked list
Public bug reported: xfdesktop is crashing when resolution is changed. It seems seamless to the user as there is nothing apparently wrong, I only noticed the problem because apport window opened later. When trying to report by it it tries to open https://bugs.launchpad.net/bugs/1787901 but I can't see that bug, so I'm making a new report. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xfdesktop4 4.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: corrupted double-linked list CasperVersion: 1.396 CurrentDesktop: XFCE Date: Wed Oct 10 17:52:41 2018 ExecutablePath: /usr/bin/xfdesktop ExecutableTimestamp: 153017 LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181009) ProcCmdline: xfdesktop ProcCwd: /home/xubuntu ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: xfdesktop4 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f4ce81ecc00 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f4ce81eacb7 "corrupted double-linked list") at malloc.c:5336 _int_malloc (av=av@entry=0x7f4ce8223c40 , bytes=bytes@entry=32768) at malloc.c:3912 __GI___libc_malloc (bytes=32768) at malloc.c:3049 png_malloc_warn () from /usr/lib/x86_64-linux-gnu/libpng16.so.16 Title: xfdesktop assert failure: corrupted double-linked list UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: xfdesktop4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash cosmic need-amd64-retrace ** Information type changed from Private 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/1797193 Title: xfdesktop assert failure: corrupted double-linked list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1797193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly
Thank you for this option. Using it the controller is working properly again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793846 Title: Regression: gamepad Redragon Seymur 2 no longer works properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly
No, because I don't know where I should apply HID_QUIRK_INCREMENT_USAGE_ON_DUPLICATE, as all search results are the commit message. Where do I apply this quirk? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793846 Title: Regression: gamepad Redragon Seymur 2 no longer works properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793846] Re: Regression: gamepad Redragon Seymur 2 no longer works properly
Unfortunately the gamepad is still with the problem. The right stick does not work properly, its up/down movement does the left/right action and left/right movement do nothing. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793846 Title: Regression: gamepad Redragon Seymur 2 no longer works properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793846] [NEW] Regression: gamepad Redragon Seymur 2 no longer works properly
Public bug reported: The gamepad Redragon Seymur 2 right analog stick no longer works properly with kernel versions at least 4.18 and newer. On 4.17.19 they work properly. I already reported this regression on kernel bugzilla but it did not receive attention there and Ubuntu Cosmic release is going to be soon, so I think it's relevant it's reported here too. This is the link of the bugzilla report I wrote: https://bugzilla.kernel.org/show_bug.cgi?id=200995 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.396 CurrentDesktop: XFCE Date: Sat Sep 22 04:14:39 2018 IwConfig: lono wireless extensions. ens2 no wireless extensions. LiveMediaBuild: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180921) Lsusb: Bus 002 Device 002: ID 0480:0200 Toshiba America Inc External Disk Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 virtiodrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.2-0-gf9626ccb91-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.0:cvnQEMU:ct1:cvrpc-i440fx-3.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.0 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793846 Title: Regression: gamepad Redragon Seymur 2 no longer works properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769247] Re: xfce4-display-settings "Primary display" option does not work properly
The issue seems like it's really not xfce4-display-settings fault, but xfce4-panel and xfdesktop that do not respect the monitor chosen as the primary one. Using Xubuntu 18.10, if I chose the Primary Monitor as the bottom monitor the desktop icons are partially hidden under the panel and the panel is still at the topmost monitor, even if I chose the bottom monitor as the Primary. It seems like xfce4-panel and xfdesktop (not sure on this one) don't deal correctly with the Primary display setting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769247 Title: xfce4-display-settings "Primary display" option does not work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1769247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778153] Re: Parole can't find the correct proportion for many videos
I just tested this, and all videos I tested are being shown with the correct proportions now. And Thunar was able to show thumbnails to all videos unless WMV videos. After install gstreamer1.0-plugins-ugly the WMV videos had thumbnails and worked properly, with their proportions right. NOTE: the Parole window that asks to install the codecs did not work, I had to install the package gstreamer1.0-plugins-ugly manually with apt. To me looks like this problem is fixed now. ** Changed in: parole (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778153 Title: Parole can't find the correct proportion for many videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1778153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788727] Re: upgrade crashing due to unsigned kernels
The package shim-signed started to fail like this one in the latest days. I have installed in my computer the following unsigned kernels: drm-tip (4.19-rc4 with multiple patches); 4.18.6 (Ubuntu mainline) 4.18-rc1 (Ubuntu mainline) 4.17.19 (Ubuntu mainline) 4.17.18 (Ubuntu mainline) 4.17.18 (not a typo, it's another build) I understand very well why I have this problem, but I have two questions related to this bug: 1) I could install mainline kernels before without this error and the system booted normally with Secure Boot enabled. Is the Secure Boot implementation of my notebook failing? 2) Would it be possible to sign new builds of the mainline kernels at kernel.ubuntu.com/~kernel-ppa/mainline/ ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788727 Title: upgrade crashing due to unsigned kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
Thank you for the effort to backport this bug fix, I have tested the proposed version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5) and the crash when changing resolution is no longer happening. Unfortunately, after some time (about 10 minutes, much longer than without this fix), the guest freezes. I reported that in https://bugs.launchpad.net/qemu/+bug/1787070 I'll change the tag to verification-done-bionic, as this particular issue was corrected. The other issue still exists in QEMU upstream. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755912 Title: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1755912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698540] Re: Parole crashes when choosing to open a file if MPRIS2 plugin is deactivated
** Changed in: parole (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698540 Title: Parole crashes when choosing to open a file if MPRIS2 plugin is deactivated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1698540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784197] Re: gnome-tweaks crash when Shift is pressed
This is the backtrace: https://paste.ubuntu.com/p/szCZq3grFW/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784197 Title: gnome-tweaks crash when Shift is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1784197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784197] Re: gnome-tweaks crash when Shift is pressed
Maybe the issue is related to the ABNT2 keyboard layout, so it doesn't happen everywhere. If it happened with all keyboard layouts, probably it would have been noticed. ** Attachment added: "Video showing the crash with the on screen keyboard" https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1784197/+attachment/5181302/+files/crashtweaks000.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784197 Title: gnome-tweaks crash when Shift is pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1784197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788630] Re: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
My problem is with the wireless card QCA9377. It has a 50% boot success rate. One time it boots, the next time it fails. On my case, I'm able to, say, install Ubuntu successfully, but after shutting the computer down and booting it again it would fail, so there is a window to act. Unfortunately I have found no way to work around this issue, the only solution being to install the mainline kernel. I have helped to investigate, even bisected the kernel, but the patch alone was not enough, as it seems the problem is complex and correctable only with many patches. After the r8169 bug I reported that was fixed to me but create an enormous regression to other users, I feel uneasy of asking to fix bugs I'm having, as they could introduce serious regressions to other users. I already use many boot parameters, mainly to enable functionalities I desire, not to work around bugs, fortunately. I use: quiet kvm.ignore_msrs=1 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt i915.enable_gvt=1 resume=UUID=0946602f- 3ca2-4379-9012-7a5171928de7 ro mtrr_gran_size=2M mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 As I want to use Intel GVT-g, cgroups and hibernation. There are options to ath10k, but found none that worked to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788630 Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 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/+bug/1788630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698540] Re: Parole crashes when choosing to open a file if MPRIS2 plugin is deactivated
Here is it more readable: http://termbin.com/xhbo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698540 Title: Parole crashes when choosing to open a file if MPRIS2 plugin is deactivated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1698540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698540] Re: Parole crashes when choosing to open a file if MPRIS2 plugin is deactivated
I'm using now Xubuntu version 18.04 that has parole version 1.0.1 and its still happening. Using gdb, it shows the following backtrace when it crashes: (gdb) bt Python Exception Installation error: gdb.execute_unwinders function is missing: Python Exception No module named 'gdb': #0 0x75ebb0a6 in g_dbus_connection_emit_signal () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #1 0x7fffe1004594 in ?? () from /usr/lib/x86_64-linux-gnu/parole-0/parole-mpris2.so Python Exception Installation error: gdb.execute_unwinders function is missing: #2 0x7fffe100480c in ?? () from /usr/lib/x86_64-linux-gnu/parole-0/parole-mpris2.so Python Exception Installation error: gdb.execute_unwinders function is missing: #3 0x76bfe15b in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #4 0x74d4af6d in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #5 0x74d5dd3e in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #6 0x74d65d8f in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #7 0x74d66e0f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #8 0x76d45b04 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #9 0x76bfd22e in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #10 0x7670e765 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #11 0x7673ef82 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #12 0x74a71287 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #13 0x74a714c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #14 0x74a717d2 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #15 0x76bfc385 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Python Exception Installation error: gdb.execute_unwinders function is missing: #16 0x5556c50b in main () Python Exception Installation error: gdb.execute_unwinders function is missing: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698540 Title: Parole crashes when choosing to open a file if MPRIS2 plugin is deactivated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1698540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788630] [NEW] package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: On the update of grub-efi-amd64, it's now warning about unsigned kernels, which it was not doing before, and failing. However, before this update, the unsigned kernels were booting properly with Secure Boot enabled. I don't know what would make them unbootable now. The following message appears on upgrade: ┌───┤ unsigned kernels ├┐ │ │ │ Cannot upgrade Secure Boot enforcement policy due to unsigned kernels │ │ │ │ Your system has UEFI Secure Boot enabled in firmware, and the following │ │ kernels present on your system are unsigned: │ │ │ │ 4.17.18-041718-lowlatency│ │ 4.17.17-041717-lowlatency│ │ │ │ │ │ These kernels cannot be verified under Secure Boot. To ensure your │ │ system remains bootable, GRUB will not be upgraded on your disk until │ │ these kernels are removed or replaced with signed kernels.│ Using the Ubuntu's default kernel is not an option to me, as it has bugs that weren't solved and make my notebook fail to boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.3 Uname: Linux 4.17.17-041717-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 23 11:30:50 2018 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-13 (435 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InvalidGrubScript: /etc/grub.d/40_custom ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.17-041717-lowlatency root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet kvm.ignore_msrs=1 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt i915.enable_gvt=1 resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 ro mtrr_gran_size=2M mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2017-10-20 (307 days ago) ** Affects: grub2 (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/1788630 Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 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/+bug/1788630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786572] [NEW] lightdm-webkit-greeter crashed with SIGSEGV in __libc_read()
Public bug reported: The login screen is subpar as it lacks many options and, when logging in Xubuntu 18.10, the webkit-greeter window appears for a few seconds and then crashes. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: lightdm-webkit-greeter 0.1.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Fri Aug 10 22:03:51 2018 ExecutablePath: /usr/bin/lightdm-webkit-greeter InstallationDate: Installed on 2018-06-21 (50 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180619) ProcCmdline: /usr/bin/lightdm-webkit-greeter ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f2029735ff6 <__run_exit_handlers+294>:mov 0x10(%rax),%rdx PC (0x7f2029735ff6) ok source "0x10(%rax)" (0x103979346acaa0) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: lightdm-webkit-greeter StacktraceTop: __libc_read (fd=12, buf=0x5573feb1e1b0, nbytes=1024) at ../sysdeps/unix/sysv/linux/read.c:27 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_io_channel_read_chars () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/liblightdm-gobject-1.so.0 Title: lightdm-webkit-greeter crashed with SIGSEGV in __libc_read() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: lightdm-webkit-greeter (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash cosmic ** Information type changed from Private 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/1786572 Title: lightdm-webkit-greeter crashed with SIGSEGV in __libc_read() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-webkit-greeter/+bug/1786572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
