[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
In Ubuntu 22.04.4 with NVidia driver 535.171.04 and windowing system X11, I downloaded and installed the packages recommended in #135: after a reboot, my terminal was fixed. Thank you @vanvugt! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
** Also affects: linux-meta-azure-6.5 (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/2038777 Title: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
Hi there, Since package linux-image-azure now install linux-image-6.5.0-1015-azure I suppose you will receive more reports about this. After inspecting linux-6.5/include/linux/hyperv.h file from linux-image- unsigned-6.5.0-1015-azure source package, I confirmed it does not have patch "hv: hyperv.h: Replace one-element array with flexible-array member" [1] applied since among others, that one was actually just picked up for upstream 6.6 as per commit "[GIT PULL] Hyper-V commits for 6.6" [2]. Hopefully the relevant commit [1] can be applied to Ubuntu 6.5 kernel soon. [1] https://lore.kernel.org/all/1692160478-18469-1-git-send-email-ssen...@linux.microsoft.com/ [2] https://lore.kernel.org/lkml/ZPQTFyfzgvlp3QkW@liuwe-devbox-debian-v2/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038777 Title: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970047] Re: GTK file open dialog hangs Chrome/Brave
The input-feedback-sounds worked for me, thanks a lot Vuk, I would never figure out that by myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970047 Title: GTK file open dialog hangs Chrome/Brave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+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 1970047] Re: GTK file open dialog hangs Chrome/Brave
This is the most annoying issue ever, I still could not find any solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970047 Title: GTK file open dialog hangs Chrome/Brave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951832] Re: xl2tpd "Can not find tunnel" in jammy
I can confirm ppa:racb/fixes fixed my VPN connection that stopped working after ubuntu 21.10 to 22.04 upgrade. What I did: apt remove xl2tpd add-apt-repository ppa:racb/fixes apt install xl2tpd network-manager-l2tp-gnome Thanks Robie! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951832 Title: xl2tpd "Can not find tunnel" in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xl2tpd/+bug/1951832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970047] Re: GTK file open dialog hangs Chrome/Brave
I've the same issue. It started to happen when I installed Ubuntu 22.04 I did a clean install not an upgrade. Everytime a file picker dialog opens it freezes the browser to any inputs. I gotta close the browser and start it again to get back working, btw I use brave. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970047 Title: GTK file open dialog hangs Chrome/Brave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969254] Re: wayland session not longer an option after recent update on Ubuntu 22.04
*** This bug is a duplicate of bug 1969243 *** https://bugs.launchpad.net/bugs/1969243 Same problem for me. NVIDIA Corporation GP108M [GeForce MX330] / Mesa Intel® Xe Graphics (TGL GT2) + driver 510. 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz × 8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969254 Title: wayland session not longer an option after recent update on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961333] [NEW] Netbook display is turned off on login screen on startup
Public bug reported: On the netbook model Positivo Mobo 5800, it was noticed that, on the end of the boot process, the LightDM greeter won't appear and the screen will turn off, disabling the backlight too. To be able to log in to the graphical interface, it's required to go to a tty (for example, tty1) and then back to the LightDM greeter (which is tty7 on this case). When going back to the tty7, it's noticed that there are text still from the boot for a few seconds, until the greeter finally appears. The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500 GPU. While gma500 is limiting, I've not observed this LightDM bug with, for example, the Positivo Mobo 5900, which has the same CPU and same GPU with the same revision and, even when applying the same image to both, the 5900 works while the 5800 fails. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 17 15:30:44 2022 ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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/1961333 Title: Netbook display is turned off on login screen on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1961333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960687] [NEW] package openjdk-11-jdk-headless:amd64 11.0.13+8-0ubuntu1~20.04 failed to install/upgrade: installed openjdk-11-jdk-headless:amd64 package post-installation script subprocess return
Public bug reported: always show this message when I try install updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openjdk-11-jdk-headless:amd64 11.0.13+8-0ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: openjdk-11-jdk-headless:amd64: Install default-jdk-headless:amd64: Install default-jdk:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Feb 5 20:06:46 2022 ErrorMessage: installed openjdk-11-jdk-headless:amd64 package post-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: openjdk-lts Title: package openjdk-11-jdk-headless:amd64 11.0.13+8-0ubuntu1~20.04 failed to install/upgrade: installed openjdk-11-jdk-headless:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openjdk-lts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960687 Title: package openjdk-11-jdk-headless:amd64 11.0.13+8-0ubuntu1~20.04 failed to install/upgrade: installed openjdk-11-jdk-headless:amd64 package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1960687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1960151] Re: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do statu
Thank you Lucas On Tue, Feb 8, 2022 at 4:25 PM Lucas Kanashiro <1960...@bugs.launchpad.net> wrote: > Thank you for taking the time to file a bug report. > > From the logs, we can see the following: > > 2022-02-05T04:58:04.67Z 1 [ERROR] [MY-012592] [InnoDB] Operating > system error number 11 in a file operation. > 2022-02-05T04:58:04.655597Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 > means 'Resource temporarily unavailable' > 2022-02-05T04:58:04.655647Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open > datafile './ibdata1' > 2022-02-05T04:58:04.655703Z 1 [ERROR] [MY-012959] [InnoDB] Could not open > or create the system tablespace. If you tried to add new data files to the > system tablespace, and it failed here, you should now edit > innodb_data_file_path in my.cnf back to what it was, and remove the new > ibdata files InnoDB created in this failed attempt. InnoDB only wrote those > files full of zeros, but did not yet use them in any way. But be careful: > do not remove old data files which contain your precious data! > 2022-02-05T04:58:04.655733Z 1 [ERROR] [MY-012930] [InnoDB] Plugin > initialization aborted with error Cannot open a file. > 2022-02-05T04:58:05.094232Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock > ./ibdata1 error: 11 > 2022-02-05T04:58:05.154836Z 1 [ERROR] [MY-010334] [Server] Failed to > initialize DD Storage Engine > 2022-02-05T04:58:05.154958Z 0 [ERROR] [MY-010020] [Server] Data Dictionary > initialization failed. > 2022-02-05T04:58:05.155482Z 0 [ERROR] [MY-010119] [Server] Aborting > > It seems that the ibdata1 file is already locked by another mysql > process, and when the process managed by the package tries to open it > you got a failure. Are you running a mysql process not managed by the > debian package? For instance, via a container. > > Since there is not enough information in your report to begin triage or to > differentiate between a local configuration problem and a bug in Ubuntu, I > am marking this bug as "Incomplete". We would be grateful if you would: > provide a more complete description of the problem, explain why you > believe this is a bug in Ubuntu rather than a problem specific to your > system, and then change the bug status back to "New". > > For local configuration issues, you can find assistance here: > http://www.ubuntu.com/support/community > > ** Changed in: mysql-8.0 (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1960151 > > Title: > package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to > install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, > o script post-installation retornou erro do status de saída 1 > > Status in mysql-8.0 package in Ubuntu: > Incomplete > > Bug description: > This bug occurance because install update Mysql > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 > ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 > Uname: Linux 5.13.0-28-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Sat Feb 5 21:49:12 2022 > ErrorMessage: o subprocesso instalado, do pacote mysql-server-8.0, o > script post-installation retornou erro do status de saída 1 > InstallationDate: Installed on 2021-12-07 (60 days ago) > InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 > (20210819) > Logs.var.log.daemon.log: > > MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] > MySQLConf.etc.mysql.conf.d.mysqldump.cnf: >[mysqldump] >quick >quote-names >max_allowed_packet = 16M > MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Muitos níveis de links > simbólicos: '/etc/mysql/my.cnf' > ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic > root=UUID=804222bf-175c-48a7-bf05-3c1e3f75f04b ro quiet splash vt.handoff=7 > Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.19.7ubuntu3 >apt 2.0.6 > SourcePackage: mysql-8.0 > Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to > install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o > script post-installation retornou erro do status de saída 1 > UpgradeStatus: No upgrade log present (probably fresh install) > modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [modified] > mtime.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: > 2022-02-05T02:14:26.568752 > > To manage notifications about this
[Bug 1960151] Re: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de
** Description changed: This bug occurance because install update Mysql ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Feb 5 21:49:12 2022 ErrorMessage: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2021-12-07 (60 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Logs.var.log.daemon.log: - + MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: - [mysqldump] - quick - quote-names - max_allowed_packet = 16M + [mysqldump] + quick + quote-names + max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Muitos níveis de links simbólicos: '/etc/mysql/my.cnf' ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=804222bf-175c-48a7-bf05-3c1e3f75f04b ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.19.7ubuntu3 - apt 2.0.6 + dpkg 1.19.7ubuntu3 + apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [modified] mtime.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: 2022-02-05T02:14:26.568752 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960151 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1960151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958405] [NEW] Ghemical crashes on Ubuntu 20.04
Public bug reported: Ghemical crashes on startup on Ubuntu 20.04: ** Affects: ghemical (Ubuntu) Importance: Undecided Status: New ** Attachment added: "triyng to run the Ghemical package" https://bugs.launchpad.net/bugs/1958405/+attachment/480/+files/Captura%20de%20tela%20de%202022-01-19%2011-13-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958405 Title: Ghemical crashes on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghemical/+bug/1958405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958404] [NEW] Gabedit crashes on Ubuntu 20.04
Public bug reported: I have installed the package Gabedit on Ubuntu 20.04 using the Ubuntu software center, and the software crashes when I try to use it. I can initialize Gabedit but they close after the navigation in the buttons begin. Until recently, Gabedit worked fine on Ubuntu, but until yesterday I couldn't use it. This packages will no longer work on Ubuntu newer versions? ** Affects: gabedit (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/1958404 Title: Gabedit crashes on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gabedit/+bug/1958404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955910] [NEW] package openjdk-17-jdk-headless:amd64 17.0.1+12-1~20.04 failed to install/upgrade: installed openjdk-17-jdk-headless:amd64 package post-installation script subprocess returned erro
Public bug reported: when I try install java 17 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openjdk-17-jdk-headless:amd64 17.0.1+12-1~20.04 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 28 09:37:51 2021 ErrorMessage: installed openjdk-17-jdk-headless:amd64 package post-installation script subprocess returned error exit status 2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: openjdk-17 Title: package openjdk-17-jdk-headless:amd64 17.0.1+12-1~20.04 failed to install/upgrade: installed openjdk-17-jdk-headless:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openjdk-17 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955910 Title: package openjdk-17-jdk-headless:amd64 17.0.1+12-1~20.04 failed to install/upgrade: installed openjdk-17-jdk-headless:amd64 package post- installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/1955910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947439] [NEW] Installation fails - grub-installer
Public bug reported: grub installer fails during installation, with 3 partitions, 45G for /, 6G for swap and 1G for ECI ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 03:12:32 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947439 Title: Installation fails - grub-installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1947439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945311] Re: Fix for CVE-2021-40438 breaks existing configs
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-0604 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945311 Title: Fix for CVE-2021-40438 breaks existing configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1945311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638410] Re: redis-server fails to start after 16.04 to 16.10 upgrade
I followed that step-by-step and it worked. https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-redis-on-ubuntu-16-04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638410 Title: redis-server fails to start after 16.04 to 16.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1638410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638410] Re: redis-server fails to start after 16.04 to 16.10 upgrade
Job for redis-server.service failed because the control process exited with error code. See "systemctl status redis-server.service" and "journalctl -xe" for details. redis-server.service: Start request repeated too quickly. redis-server.service: Failed with result 'exit-code'. Failed to start Advanced key-value store. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638410 Title: redis-server fails to start after 16.04 to 16.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1638410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638410] Re: redis-server fails to start after 16.04 to 16.10 upgrade
This problem did not occur in version 20.04 LTS. But as soon as I upgraded to version 21.04 it started to happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638410 Title: redis-server fails to start after 16.04 to 16.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1638410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926152] [NEW] version upgrade did not work
Public bug reported: I am trying to upgrade from 18.04 to 20.04.2 LTS but he upgrade fails with message: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Mon Apr 26 08:59:04 2021 InstallationDate: Installed on 2011-05-11 (3637 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-04-26 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926152 Title: version upgrade did not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1926152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924882] Re: Random freezing of the computer during testing.
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 I downloaded the Ubuntu 20.04 iso and made a boot running from it. Everything works normal. So I deduced that the problem is in updating third parties, something broke the video driver. I did a new installation of Ubuntu 20.04 and its updates, installed my tools and lib required for my work. It's working well so far. Thank you for your attention and help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924882 Title: Random freezing of the computer during testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1924882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924882] [NEW] Random freezing of the computer during testing.
Public bug reported: I1m using UBUNTU 20.04 Problem: Occasionally there is a failure to display on the screen with parts alternating colors and characters exchanged in the terminal (only in the terminal). Control characters are displayed on the terminal and "blink" effects occur on some lines. First symptom: The firefox update made the browser screen (just inside the browser screen) appear many black blocks over the texts and images, corrected with the deactivation of the use of graphical acceleration. Second symptom: after an update of ubuntu, he started to have a problem in the terminal, with control characters being displayed and a change in the mapping of the keyboard keys BUT this error does not happen in GEdit. Current symptom: when I open the terminal, the favorite icons on the edge of the screen where the terminal was opened change color alternately. The terminal screen has control characters and changes from character mapping to some keys. The browser is not fluent in scrolling a web page. Reboot the computer everything is normal and after a while it happens again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Apr 17 22:13:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:100d] InstallationDate: Installed on 2021-02-23 (53 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. K46CA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ec0afab4-cb78-44a3-8868-cf6565dfb058 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K46CA.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K46CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK46CA.315:bd05/17/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K46CA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924882 Title: Random freezing of the computer during testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920627] [NEW] wifi manager not work correctly with budgie
Public bug reported: in budgie the wifi is connected but when I go to search for a site with the browser it does not connect ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-67.75~18.04.1-generic 5.4.94 Uname: Linux 5.4.0-67-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 CurrentDesktop: Budgie:GNOME Date: Sat Mar 20 18:23:43 2021 InstallationDate: Installed on 2021-03-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) SourcePackage: linux-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920627 Title: wifi manager not work correctly with budgie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1920627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915650] Re: QTerminal drop-down shortcut with unmaped key breaks keyboard input
** Also affects: xorg-server 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/1915650 Title: QTerminal drop-down shortcut with unmaped key breaks keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1915650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915650] [NEW] QTerminal drop-down shortcut with unmaped key breaks keyboard input
Public bug reported: [Originally submitted to https://github.com/lxqt/qterminal/issues/794] Setting the global shortcut of QTerminal drop-down to a (valid) key that isn't mapped to any physical key in the current keyboard layout (ex.: F13) makes QTerminal capture and consume all presses from all X windows(!). Additionally, it seems that if the shortcut is set to an invalid value (ex.: "Spam") using the settings dialog, instead of causing an error, the shortcut is actually set to the Delete key. These bugs happen on both X and Wayland sessions (with QTerminal running under XWayland in the latter case) and I was able to reproduce it on a different Ubuntu 20.04 machine. QTerminal devs (see link above) weren't able to reproduce using a newer release/different setup, though the code dealing with X11 global shortcut wasn't really modified in the last years. # Expected Behavior For the valid but unmapped key case, the shortcut would not work, of course. But QTerminal should not consume the keypresses. For the invalid key case, it should show an error message on clicking "Apply" or "OK", don't register the shortcut and either undo the setting or clear the shortcut. # Steps to Reproduce 1. Launch QTerminal in drop-down mode 2. Open Preferences > Dropdown > Shortcut 3. Set the global shortcut to a valid key that doesn't exist in the current keyboard layout (ex.: F13) and apply 4. Close the preferences dialog and try to type text in the terminal or any other program's window (it shouldn't work) 5. Open a "system monitor" using the mouse and kill the qterminal process (keyboard should start working again) 6. Map some key to the problematic key used in step (3) with xmodmap: $ xmodmap -e 'keysym Escape = F13' 7. Repeat the steps (1) to (4) and verify that the buggy behavior disappeared # Context I hit this problem after upgrading my system from 18.04 to 20.04. I have modified the layout file for the keyboard layout that I use to remap the Caps Lock key to Escape and the Escape key to F13, so that I could use it exclusively as a drop-down terminal shortcut. The upgrade overwrote the layout file and undid my modifications. I had QTerminal dropdown set as an startup app and, suddenly, when I logged in the first time after the upgrade, my keyboard didn't work anymore! It took me a couple days of tracking down to figure out that QTerminal was to blame, but at least it was easy to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qterminal 0.14.1-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Feb 14 11:31:03 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 InstallationDate: Installed on 2021-01-05 (40 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: qterminal UpgradeStatus: Upgraded to focal on 2021-02-10 (3 days ago) ** Affects: qterminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session x-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915650 Title: QTerminal drop-down shortcut with unmaped key breaks keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1915650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817785] Re: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc'
This is affecting me in a fresh Ubuntu 18.04 installation. Thank's for the temporary solution, @Ernst. Here is a related question (made 9 months prior to this bug report openning) on the TeX StackExchange website: https://tex.stackexchange.com/questions/431244/texdoc-does-not-work- anymore-after-ubuntu-upgrade/580678 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817785 Title: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1817785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913614] [NEW] package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: This happens when running do-release-upgrade to last Ubuntu version The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Setting up grub-efi-amd64-signed (1.142.10+2.04-1ubuntu26.8) ... Unknown device "/dev/disk/by-id/*": No such file or directory dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent processing triggers for shim-signed: shim-signed depends on grub-efi-amd64-signed | grub-efi-arm64-signed; however: Package grub-efi-amd64-signed is not configured yet. Package grub-efi-arm64-signed is not installed. dpkg: error processing package shim-signed (--configure): dependency problems - leaving triggers unprocessed Errors were encountered while processing: grub-efi-amd64-signed shim-signed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: skip Date: Thu Jan 28 12:56:56 2021 DuplicateSignature: package:shim-signed:1.40.4+15+1552672080.a4a1fbe-0ubuntu2 Setting up grub-efi-amd64-signed (1.142.10+2.04-1ubuntu26.8) ... Unknown device "/dev/disk/by-id/*": No such file or directory dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 EFITables: Jan 28 12:28:12 ROBO-03 kernel: efi: EFI v2.70 by EDK II Jan 28 12:28:12 ROBO-03 kernel: efi: SMBIOS=0x7f7ac000 ACPI=0x7f97e000 ACPI 2.0=0x7f97e014 MEMATTR=0x7e91a018 Jan 28 12:28:12 ROBO-03 kernel: secureboot: Secure boot disabled Jan 28 12:28:12 ROBO-03 kernel: secureboot: Secure boot disabled ErrorMessage: dependency problems - leaving triggers unprocessed GrubDiff: Binary files /boot/efi/EFI/ubuntu/grubx64.efi and /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed differ Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: shim-signed Title: package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to focal on 2021-01-28 (0 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913614 Title: package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1913614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912725] [NEW] package linux-modules-extra-5.8.0-40-generic (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.8.0-40-generic.list-new'
Public bug reported: After update my DisplayLink device (HP 3005pt USB 3.0 Port Replicator)stopped working. I can see it connected, USB, all other devices, except video don't come up. https://support.displaylink.com/knowledgebase/articles/683672-my- displaylink-device-does-not-work-on-ubuntu I am trying different ways to get it working back. I have a dual boot laptop and on Windows device is working just fine, so no device issue. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.8.0-40-generic (not installed) ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 22 15:01:42 2021 DuplicateSignature: package:linux-modules-extra-5.8.0-40-generic:(not installed) Unpacking linux-modules-5.8.0-40-generic (5.8.0-40.45~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-eUy6zR/14-linux-modules-5.8.0-40-generic_5.8.0-40.45~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-40-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.8.0-40-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-05-30 (236 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: linux-hwe-5.8 Title: package linux-modules-extra-5.8.0-40-generic (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.8.0-40-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912725 Title: package linux-modules-extra-5.8.0-40-generic (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-extra-5.8.0-40-generic.list-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1912725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876503] Re: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on)
Hello Chris. After all this time i found that when this happens, i can "solve" it pressing the same combination of keys that caused it. It happens to me when i use Function(Fn) key plus the key that makes volume up (+vol), makes it go down (-vol) or sometimes when i press the mute key.(mute) For example, if i was lowing the sound and the problem happens, my keyboard stops responding and my volume goes to 0%, even if i was in ,lets say 70%, and i tried to go to 67%(i need to press the key only one time to make that). If the keyboard becomes "locked", i need to press again Fn+(-vol) key several times to "recover" the keybaord again, and after that i can use it normally. The same happens sometimes with mute key and (+vol) key, is a bit strange thing to explain for me. I don't know what could makes this happen, since it happened to me in 18.04 an 20.04 too. I managed myself to press again the 2 keys that i pressed before the keyboard becomes locked, so it is just an annoying thing, not a big error as you have said. About the other combinations of keys, when this happens i only can press the key combination that triggered the "keyboard lock", and other keys does not work. The mouse, at the contrary, works perfectly and that is why i managed myself to discover that log off and log in again solves my problem the 1st time i discovered it. I found in the !shourcut keys" that these actions are related to this commands: XF86AudioMute XF86AudioRaiseVolume XF86AudioLowerVolume Maybe there is something wrong with those command and my hardware,but i don't have idea about that. Thanks for see the topic and take a moment to answer me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876503 Title: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902682] [NEW] I could not update Ubuntu to 20.04, fail in the 2nd step
Public bug reported: I followed the automatic update and while estimating the time for the update it failed, due to some third party software that is installed in my machine. I tried using ppa-purge but did not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Nov 3 10:29:06 2020 InstallationDate: Installed on 2018-10-05 (759 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-03 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902682 Title: I could not update Ubuntu to 20.04, fail in the 2nd step To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1902682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901196] Re: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)]
I tried: cd /usr/src/linux-headers-5.8.0-25-generic sudo make oldconfig YACC scripts / kconfig / parser.tab. [Ch] HOSTCC scripts / kconfig / lexer.lex.o HOSTCC scripts / kconfig / parser.tab.o HOSTCC scripts / kconfig / preprocess.o HOSTCC scripts / kconfig / symbol.o HOSTCC scripts / kconfig / util.o HOSTLD scripts / kconfig / conf scripts / kconfig / conf --oldconfig Kconfig # # configuration written to .config # And later: sudo make prepare scripts / kconfig / conf --syncconfig Kconfig make [1]: *** There is no rule to build the target 'arch / x86 / tools / relocs_32.c', necessary for 'arch / x86 / tools / relocs_32.o'. High. make: *** [arch / x86 / Makefile: 211: archscripts] Error 2 Is it here the bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901196 Title: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901196] Re: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)]
Hello, I'm the same. I started researching and tried: sudo dkms --verbose build -m nvidia-340 -v 340.108 and it returned the same error. Since I still have an old kernel installed I tried: sudo dkms --verbose build -m nvidia-340 -v 340.108 -k 5.4.0-26-generic and it worked perfect, just for that kernel. I don't have much knowledge, and I don't know where the error can be with the 5.8.0-25-generic kernel. Note: I just upgraded Ubuntu to Groovy, everything worked fine except nvidia-340. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901196 Title: kernel module failed to build [ Bad return status for module build on kernel: 5.8.0-25-generic (x86_64)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
I am running Ubuntu in x11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
Looking at my plugins I have both "MediaServer3 D-Bus Interface" and "MPRIS D-Bus Interface" activated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
launching with rhythmbox --disable-plugins does not allow for media buttons at all. When trying to use one the 'no entry' sign show up on the screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890632] [NEW] Can't open preferences
Public bug reported: I can't seem to access the rhymbox preferences. 'Preferences' does not appear in the application menu (see attachment) since ubuntu 17.10. I was still able to edit the preferences from the menu under the song slider, but I have now accidentally removed the whole top bar (with the current song, the previous, next, pause buttons, and that menu button). So now I can't open the preferences, nor see the current song anymore, or have it display again. Note that the option in the view menu might have been from the Alternative-Toolbar plugin A temporary fix to get the view menu again would be appreciated too. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 Version table: *** 3.4.4-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Mirror of the attachment (screenshot of the application menu): https://i.imgur.com/CJUVoRZ.png ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "rhythmbox no preferences.png" https://bugs.launchpad.net/bugs/1890632/+attachment/5399332/+files/rhythmbox%20no%20preferences.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890632 Title: Can't open preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
After restarting the machine, launching rhythmbox from the command line does not print messages. Subsequent launches do however -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890494] Re: Closing Rhythmbox does not free the media keys
I am talking about the pause/play, previous song and next song keys. On my Dell xps 13 laptop, those are f4, f5 and f6 (or fn + f4, fn + f5, fn + f6) When opening Rhythmbox from the command line: (this is after having opened and closed it once, so the media keys were already not working) Opening and using rhythmbox does not print error messages, but closing does: /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '12157' return func(*args, **kwargs) /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '12156' return func(*args, **kwargs) /usr/lib/python3/dist-packages/gi/overrides/GObject.py:502: Warning: ../../../gobject/gsignal.c:2735: instance '0x5635f68af300' has no handler with id '40060' return func(*args, **kwargs) I will now restart my machine to launch rhythmbox the first time from the command line (with working media keys) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890494] [NEW] Closing Rhythmbox does not free the media keys
Public bug reported: Closing Rhythmbox, does not free the media keys, and no program can use them after that, not even Rhythmbox if you restart it. This seems to be very close to bug #1036489, but that one was active 8 years ago, and was marked as expired 6 years ago. Restarting the machine frees the media keys again. Steps to reproduce: 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 Version table: *** 3.4.4-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: rhythmbox (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/1890494 Title: Closing Rhythmbox does not free the media keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036489] Re: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key-binding behavior
This still affects me in Ubuntu 20.04. Fully closing Rhythmbox does not free up the media keys, and if you reopen it later the media keys will not work (and won't work for other programs either) Different ways to reproduce (note that the only way to have the media keys working again is to restart the machine) 1. Verify that the media keys work (restart the machine if not) 2. close rhythmbox with right click on the taskbar icon, use "stop & quit" 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. End the 'rhythmbox' process 3. reopen rhythmbox, the media keys do not work. 1. Verify that the media keys work (restart the machine if not) 2. in rhythmbox go to preferences -> plugins -> click preferences for any plugin 3. click the 'restart' next to "Restart the player for the changes to take effect" 4. once rhythmbox restarts, the media keys do not work anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036489 Title: Closing Rhythmbox doesn't close Rhythmbox and causes confusing key- binding behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1036489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887257] Re: update-grub does not create any entry on grub.cfg for ZFS on root
Also, please close this issue as Not a bug. I reverted the state of symlink and it did well with dash. The issue in fact is what changed the default kernel, since manual change was made by me. After a dpkg-reconfigure dash and selecting the dash as sh link, things does well again. I can't tell what in fact changed default sh to bash, but its another issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887257 Title: update-grub does not create any entry on grub.cfg for ZFS on root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1887257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887257] Re: update-grub does not create any entry on grub.cfg for ZFS on root
Hello Julian, I did not changed by my own the point of /bin/sh but in fact you're correct root@manauara:~# ls -lah /bin/sh lrwxrwxrwx 1 root root 4 jun 3 22:19 /bin/sh -> bash What is the correct way to fix this issue? Also, may not all scripts of Ubuntu that depends on dash syntax point to dash directly? There is a way I can check who is the package that changed that link? root@manauara:~# update-alternatives --get-selections | grep ^sh ; echo $? 1 root@manauara:~# (I've tried to found something inside scripts at /var/lib/dpkg/info but without success until now). How can I find who changed the shell? If its an official package, I'll send the bug report about changing sh symlink. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887257 Title: update-grub does not create any entry on grub.cfg for ZFS on root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1887257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887257] Re: update-grub does not create any entry on grub.cfg for ZFS on root
Hello! I did a deeper troubleshoot and found an issue with 10_linux_zfs script. I created the attached patch and it fixed the issue. Can you please check this patch? Leonardo ** Patch added: "Patch for echo -e issue at 10_linux_zfs" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1887257/+attachment/5394378/+files/grub_1887257_patch.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887257 Title: update-grub does not create any entry on grub.cfg for ZFS on root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1887257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887257] [NEW] update-grub does not create any entry on grub.cfg for ZFS on root
Public bug reported: I observed after a lot of updates my kernel did not get update after reboot. I found my /boot zfs pool not mounted properly and re-imported it, but when I generate new grub.cfg, the 10_linux_zfs section is empty, even with /boot mounted properlly: root@manauara:~# zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1,88G 196M 1,68G- - 0%10% 1.00xONLINE - rpool 114G 43,8G 70,2G- -46%38% 1.00xONLINE - root@manauara:~# mount | grep boot bpool/BOOT/ubuntu_bpn5ci on /boot type zfs (rw,nodev,relatime,xattr,posixacl) /dev/sdb1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/sdb1 on /boot/grub type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) root@manauara:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # /boot/efi was on /dev/sdb1 during installation UUID=3663-2075 /boot/efi vfatumask=0022,fmask=0022,dmask=0022 0 1 /boot/efi/grub /boot/grub nonedefaults,bind 0 0 UUID=9b5b207e-da46-4b16-b827-d8521151c8bf noneswapdiscard 0 0 root@manauara:~# cat /etc/zfs/zfs-list.cache/bpool bpool /boot off on on off on off on off - none bpool/BOOT noneoff on on off on off on off - none bpool/BOOT/ubuntu_bpn5ci/boot on on on off on off on off - none I have cleaned all snapshots because another issue with zsys and images, so my snapshot tree is almost clean: root@manauara:~# zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT bpool/BOOT/ubuntu_bpn5ci@autozsys_n55ov3 90,6M - 104M - rpool/ROOT/ubuntu_bpn5ci@autozsys_n55ov3 43,5M - 6,22G - rpool/ROOT/ubuntu_bpn5ci/srv@autozsys_n55ov3 0B - 96K - rpool/ROOT/ubuntu_bpn5ci/usr@autozsys_n55ov3 0B - 96K - rpool/ROOT/ubuntu_bpn5ci/usr/local@autozsys_n55ov3 0B - 2,94M - rpool/ROOT/ubuntu_bpn5ci/var@autozsys_n55ov3 0B - 96K - rpool/ROOT/ubuntu_bpn5ci/var/games@autozsys_n55ov3 0B - 96K - rpool/ROOT/ubuntu_bpn5ci/var/lib@autozsys_n55ov3 464K - 7,93G - rpool/ROOT/ubuntu_bpn5ci/var/lib/AccountsService@autozsys_n55ov3 0B - 336K - rpool/ROOT/ubuntu_bpn5ci/var/lib/NetworkManager@autozsys_n55ov3116K - 168K - rpool/ROOT/ubuntu_bpn5ci/var/lib/apt@autozsys_n55ov3 136K - 95,7M - rpool/ROOT/ubuntu_bpn5ci/var/lib/dpkg@autozsys_n55ov3 2,32M - 55,2M - rpool/ROOT/ubuntu_bpn5ci/var/log@autozsys_n55ov3 7,54M - 1,13G - rpool/ROOT/ubuntu_bpn5ci/var/mail@autozsys_n55ov30B - 96K - rpool/ROOT/ubuntu_bpn5ci/var/snap@autozsys_n55ov30B - 2,17M - rpool/ROOT/ubuntu_bpn5ci/var/spool@autozsys_n55ov3 56K - 208K - rpool/ROOT/ubuntu_bpn5ci/var/www@autozsys_n55ov3 0B - 96K - rpool/USERDATA/leonardo_xoeglb@autozsys_n55ov316,8M - 27,0G - rpool/USERDATA/leonardo_xoeglb@autozsys_qc46s77,86M - 27,0G - rpool/USERDATA/root_xoeglb@autozsys_n55ov3 132K - 1,17G - The output of upgrade-grub (With sh -x in 10_linux_zen) is attached and other system information is at ubuntu-bug report attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub2-common 2.04-1ubuntu26 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 20:24:10 2020 InstallationDate: Installed on 2020-04-27 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Output of update-grub while 10_linux_zfs contains sh -x in first line"
[Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Improving Mike's above feedback, I've realized that connecting the external monitor directly to the laptop HDMI port really make things run normally, but when I turned off the OS extend desktop to external monitor function(HDMI), I can keep the Docktation connected with 2 monitors on it without problems... My environment has 3 monitors, 2 on Dock station and 1 on laptop's HDMI port... For now, I can work without any problems Mike, thanks for the tip!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1875015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880325] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1880325/+attachment/5376653/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1880325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880325] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880325/+attachment/5376652/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1880325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880325] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880325/+attachment/5376651/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1880325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880325] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880325/+attachment/5376654/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1880325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880325] Re: Intel Wireless Centrino N100 error in Txrate and Bitrate
apport information ** Tags added: apport-collected ** Description changed: In the last week install a Xubuntu 18.04 distro in the netbook of my brother this install all fine but the Intel Centrino Wireless N100 card doesnt work good because the Bitrate mark 24 and Txrate 14 all time the unique way to connect to the signal of router its put near this. I search in the net in Google to resolve this conflict and fix this explain in the lines below the procedure to obtain this. First this Issue affects this models of Intel Wireless: Wi-Fi 6 products Intel® Wi-Fi 6 AX200 (5.1) Intel® Wi-Fi 6 AX201 (5.2) 802.11ac products Intel® Wireless-AC 9462 (4.14) Intel® Wireless-AC 9461 (4.14) Intel® Wireless-AC 9260 (4.14) Intel® Wireless-AC 9560 (4.14) Intel® Wireless-AC 8265 (4.6) Intel® Wireless-AC 3168 (4.6) Intel® Wireless-AC 8260 (4.1) Intel® Wireless-AC 3165 (4.1) 802.11n or 802.11ac products (SKU dependent) Intel® Wireless 7265 (3.13) Intel® Wireless 7260 (3.10) Intel® Wireless 3160 (3.10) 802.11abgn products Intel® Centrino® Advanced-N 6235 (3.2) Intel® Centrino® Advanced-N 6230 (2.6.36) Intel® Centrino® Advanced-N 6205 (2.6.35) Intel® Centrino® Advance-N + WiMAX 6150 (2.6.30) Intel® Centrino® Advanced-N + WiMAX 6250 (2.6.30) Intel® Centrino® Ultimate-N 6300 (2.6.30) Intel® Centrino® Advanced-N 6200 (2.6.30) Intel® WiMAX/Wi-Fi Link 5350 (2.6.27) Intel® Ultimate N Wi-Fi Link 5300 (2.6.27) Intel® WiMAX/Wi-Fi Link 5150 (2.6.29) Intel® Wi-Fi Link 5100 Series (2.6.27) 802.11bgn products Intel® Centrino® Wireless-N 2230 (3.2) Intel® Centrino® Wireless-N 2200 (3.2) Intel® Centrino® Wireless-N 105 (3.2) Intel® Centrino® Wireless-N 135 (3.2) Intel® Centrino® Wireless-N 100 (2.6.37) Intel® Centrino® Wireless-N 130 (2.6.37) Intel® Centrino® Wireless-N 1030 (2.6.36) Intel® Centrino® Wireless-N 1000 (2.6.30) Second need to go to this page and download the firmware of the model affected: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi Third decompress the tar in the download folder and us this command in the terminal: cp iwlwifi-*.ucode /lib/firmware Later reboot the machine and enter again Four open a terminal windows and enter the following command: sudo nano /etc/NetworkManager/NetworkManager.conf put this line into the file [device] wifi.scan-rand-mac-address=no save and reboot the Network Manager or reboot the machine Five open a terminal windows and enter the following command: sudo nano /etc/network/interfaces you see hte file equal this: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Substitute eth0 for the driver of your wireless card use in the terminal ifconfig to see Restart Network Manager services or reboot the machine Six edit DNS config file open the terminal and put the following command: sudo nano/etc/resolv.conf Add this lines to the file exactly: # Google IPv4 nameservers nameserver 8.8.8.8 nameserver 8.8.4.4 1 2 3 4 5 # Google IPv6 nameservers nameserver 2001:4860:4860:: nameserver 2001:4860:4860::8844 save and close and restart the machine Ready the Bug its fixed + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: leonardo 1074 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-05-25 (0 days ago) + InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) + MachineType: Intel Corporation Intel powered classmate PC + Package: linux-meta (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c103aee1-118e-4dcd-88e2-e9871fdc8081 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173.18 + Tags: bionic + Uname: Linux 4.15.0-20-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/16/2011 + dmi.bios.vendor: Phoenix + dmi.bios.version: BPPNV10A.86A.0015.2011.0516.1530 + dmi.board.asset.tag: PTL Nanjing + dmi.board.name: Intel powered classmate PC + dmi.board.vendor: Intel Corporation + dmi.board.version: MP PV + dmi.chassis.type: 10 + dmi.chassis.vendor: Intel + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenix:bvrBPPNV10A.86A.0015.2011.0516.1530:bd05/16/2011:svnIntelCorporation:pnIntelpoweredclassmatePC:pvrBPPV:rvnIntelCorporation:rnIntelpoweredclassmatePC:rvrMPPV:cvnIntel:ct10:cvrN/A: + dmi.product.name: Intel powered cl
[Bug 1880340] [NEW] Samba Bug delete gvfs-backends
Public bug reported: Other Bug in the 18.04 Distribution I explain the cause of this error About 3 months ago install samba all be good but delete the samba application but have and error a dialog box appears when I click in search net a circle red and tell me impossible mount / I search in the net and the problem resolve in this form: userspace virtual filesystem - backends gvfs is a userspace virtual filesystem where mounts run as separate processes which you talk to via D-Bus. It also contains a gio module that seamlessly adds gvfs support to all applications using the gio API. It also supports exposing the gvfs mounts to non-gio applications using fuse. userspace virtual filesystem - backends gvfs is a userspace virtual filesystem where mounts run as separate processes which you talk to via D-Bus. It also contains a gio module that seamlessly adds gvfs support to all applications using the gio API. It also supports exposing the gvfs mounts to non-gio applications using fuse. Detailed Instructions: Step 1 Run update command to update package repositories and get latest package information. sudo apt-get update -y Step 2 Run the install command with -y flag to quickly install the packages and dependencies. sudo apt-get install -y gvfs-backends Its all and fix the error ** Affects: sgml-base (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/1880340 Title: Samba Bug delete gvfs-backends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1880340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880325] Re: Intel Wireless Centrino N100 error in Txrate and Bitrate
Your Welcome other things I see in the Distro wrote -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1880325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879997] [NEW] HP-255-G7-Notebook-PC 5.3.0-51-generic
Public bug reported: HP-255-G7-Notebook-PC System wont reboot or shutdown after kernel 5.3.0-53 update ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879997 Title: HP-255-G7-Notebook-PC 5.3.0-51-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879109] [NEW] Olá, aopos a atualização de distribuição, todos os navegadores apresentam falha na conexão com a internet; porém a rede permanece conectada sem qualquer problema a rede wi-fi ou po
Public bug reported: Olá, apos a atualização de distribuição, todos os navegadores apresentam falha na conexão com a internet; porém a rede permanece conectada sem qualquer problema a rede wi-fi ou por conexão à cabo. Apos clicar por algumas vezes no atualizar retorna a conexão do navegador com a internet. Ubuntu atualizado para a versão mais recente 2020 da distribuição; apos a atualização problema surgiu. instalado diferentes navegadores bem como efetuado teste no navegador nativo, problema persiste. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat May 16 21:23:11 2020 InstallationDate: Installed on 2018-07-06 (680 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2020-05-14 (2 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879109 Title: Olá, aopos a atualização de distribuição, todos os navegadores apresentam falha na conexão com a internet; porém a rede permanece conectada sem qualquer problema a rede wi-fi ou por conexão à cabo. Apos clicar por algumas vezes no atualizar retorna a conexão do navegador com a internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1879109/+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 1869588] Re: WiFi performance is slow
*** This bug is a duplicate of bug 1869587 *** https://bugs.launchpad.net/bugs/1869587 Performance improved after removing this package. +1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869588 Title: WiFi performance is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1869588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876503] Re: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on)
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+attachment/5365253/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876503 Title: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876503] Re: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on)
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+attachment/5365252/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876503 Title: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876503] [NEW] Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log o
Public bug reported: My keyboard stop responding randomly, sometimes during High ram consume, and other times during idling(no high demanding programs opened), when this happen i need to log out and log in again or reset the pc. The mouse is working normally under this "status" where keyboard isnt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxqt-config 0.14.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sat May 2 15:07:23 2020 InstallationDate: Installed on 2020-04-29 (2 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-config (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/1876503 Title: Keyboard input suddenly stops to work, but when i log off and relog it comes back to normal.(I cant use keyboard after the bug happens, but i can do it normaly after log out- log on) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1876503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875767] Re: When operating install/removal with apt, zed floods log and apparently crashes snapshoting
As recommended by sarnold@#ubuntu-devel.freenode, pasting entire apt command and output. It happened other times I did instalations too: root@manauara:~# apt install pulseaudio-modules-bt libldac Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto The following additional packages will be installed: libfdk-aac1 Pacotes sugeridos: libavcodec Os pacotes a seguir serão REMOVIDOS: pulseaudio-module-bluetooth Os NOVOS pacotes a seguir serão instalados: libfdk-aac1 libldac pulseaudio-modules-bt 0 pacotes atualizados, 3 pacotes novos instalados, 1 a serem removidos e 0 não atualizados. É preciso baixar 469 kB de arquivos. Depois desta operação, 827 kB adicionais de espaço em disco serão usados. Você quer continuar? [S/n] S Obter:1 http://br.archive.ubuntu.com/ubuntu focal/multiverse amd64 libfdk-aac1 amd64 0.1.6-1 [366 kB] Obter:2 http://ppa.launchpad.net/eh5/pulseaudio-a2dp/ubuntu disco/main amd64 libldac amd64 2.0.2.3-2~disco1 [28,1 kB] Obter:3 http://ppa.launchpad.net/eh5/pulseaudio-a2dp/ubuntu disco/main amd64 pulseaudio-modules-bt amd64 1.1.99-3~disco1 [74,3 kB] Baixados 469 kB em 2s (242 kB/s) ERROR rpc error: code = DeadlineExceeded desc = context deadline exceeded (Lendo banco de dados ... 175329 ficheiros e directórios actualmente instalados.) A remover pulseaudio-module-bluetooth (1:13.99.1-1ubuntu3) ... A seleccionar pacote anteriormente não seleccionado libfdk-aac1:amd64. (Lendo banco de dados ... 175318 ficheiros e directórios actualmente instalados.) A preparar para desempacotar .../libfdk-aac1_0.1.6-1_amd64.deb ... A descompactar libfdk-aac1:amd64 (0.1.6-1) ... A seleccionar pacote anteriormente não seleccionado libldac:amd64. A preparar para desempacotar .../libldac_2.0.2.3-2~disco1_amd64.deb ... A descompactar libldac:amd64 (2.0.2.3-2~disco1) ... A seleccionar pacote anteriormente não seleccionado pulseaudio-modules-bt. A preparar para desempacotar .../pulseaudio-modules-bt_1.1.99-3~disco1_amd64.deb ... A descompactar pulseaudio-modules-bt (1.1.99-3~disco1) ... Configurando libldac:amd64 (2.0.2.3-2~disco1) ... Configurando libfdk-aac1:amd64 (0.1.6-1) ... Configurando pulseaudio-modules-bt (1.1.99-3~disco1) ... A processar 'triggers' para libc-bin (2.31-0ubuntu9) ... ERROR rpc error: code = Unavailable desc = transport is closing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875767 Title: When operating install/removal with apt, zed floods log and apparently crashes snapshoting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875767] [NEW] When operating install/removal with apt, zed floods log and apparently crashes snapshoting
Public bug reported: Hello! When I ran a install, it behaved like this: ERROR rpc error: code = DeadlineExceeded desc = context deadline exceeded ... etc apt messages ... A processar 'triggers' para libc-bin (2.31-0ubuntu9) ... ERROR rpc error: code = Unavailable desc = transport is closing Log gets flooded by the follow message: abr 28 20:41:48 manauara zed[512257]: eid=10429 class=history_event pool_guid=0x7E8B0F177C4DD12C abr 28 20:41:49 manauara zed[508106]: Missed 1 events And machine load gets high for incredible amount of time. Workarround is: systemctl restart zsysd systemctl restart zed System also gets a bit slow and fans get high for a while (because the load). This is a fresh install of ubuntu 20.04 with ZFS on SATA SSD. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 28 20:49:14 2020 InstallationDate: Installed on 2020-04-27 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (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/1875767 Title: When operating install/removal with apt, zed floods log and apparently crashes snapshoting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875767/+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 1867669] [NEW] Option EmulateThirdButtonTimeout does not work
Public bug reported: I am trying to configure the following touchscreen: Bus 004 Device 002: ID 22b9:0005 eTurboTouch Technology, Inc. And I have noticed that the option EmulateThirdButtonTimeout has no effect if set to a value above 750. If set to lower values, as 500, 250 or even 1, the behaviour changes, but values above 750 have no effect, keeping the behaviour as 750. I would like to set to a higher value, as 2000, for example. Also, it creates a second device, identified as a mouse, that has no function, but the system tries to use by default, requiring a Xorg configuration to ignore it. This touchscreen doesn't work with libinput, working only with evdev. The current Xorg configuration contains: Section "InputClass" Identifier "HID Touchscreen" MatchUSBID "22b9:0005" Driver "evdev" Option "EmulateThirdButton" "1" Option "EmulateThirdButtonTimeout" "2500" Option "EmulateThirdButtonThreshold" "20" Option "Emulate3Buttons" "false" Option "ButtonMapping" "1 3 3 0 0 0 0 0 0 0 0 0 0 0" EndSection Section "InputClass" Identifier "TouchButMouse" MatchProduct "HID TOUCH HID Touch Panel Mouse" Option "Ignore" "true" EndSection ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-evdev-hwe-18.04 1:2.10.6-1~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 16 16:09:00 2020 SourcePackage: xserver-xorg-input-evdev-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-input-evdev-hwe-18.04 (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/1867669 Title: Option EmulateThirdButtonTimeout does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev-hwe-18.04/+bug/1867669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867319] Re: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"
Edit on the previous comments, the processes are not owned by the user, processes are owned by root but ps returns several lines like: /usr/lib/policykit-1/polkit-agent-helper-1 USERNAME where USERNAME is the user that gets stuck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867319 Title: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1867319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867319] Re: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"
I see that the user has tens of /usr/lib/policykit-1/polkit-agent- helper-1 processes running, which seems to be part of the policykit-1 package ** Package changed: ubuntu => policykit-1 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867319 Title: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1867319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867319] [NEW] Can not access desktop after switching user: stuck at "authentication required to refresh system repositories"
Public bug reported: When switching from the user (sudo-enabled) I normally use to another one (which I rarely use, and is also sudo-enabled), I can not access the desktop. A window opens blocking the whole screen and asking the user password (the second user), whatever I type, the window does not close (see screenshot). In some cases after a random number of times I push "cancel" the window disappears, but not all the times. Steps to reproduce the bug: - switch from user A to user B - enter password in gdm, log-in is successful - update window opens and never disappears. I can not access the desktop. To exit this situation I need to change desktop with CTRL+ALT+F4 and log-in again with user A, which works. If I switch to user B again I am stuck again. Note that after this happens, I updated/upgraded repositories using user A and the window will be still there when switching to user B. What you expected to happen: - If I enter the user password the window should do something (start updating) but instead it produces an error (something on the line "This did not work") and the window remains there - If I push "cancel" the window remains there, only in some cases it did disappear after clicking cancel many times (tens of times) I'v seen this page describing something similar, but I don't have xRDP installed https://c-nergy.be/blog/?p=14051 $ dpkg -l| grep -i xrdp $ Ubuntu Version: packages updated to March 13 2020. No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan GNOME: 3.34.2 Graphics: Intel UHD Graphics (Whiskey Lake 3x8 GT2) ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "bug.png" https://bugs.launchpad.net/bugs/1867319/+attachment/5336410/+files/bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867319 Title: Can not access desktop after switching user: stuck at "authentication required to refresh system repositories" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1867319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867033] [NEW] Kernel BUG when loading classmate_laptop, accelerometer does not work
Public bug reported: When trying to load the classmate_laptop module to enable the accelerometer, a kernel BUG is happening and the accelerometer isn't loaded. This problem was observed more often when reloading the classmate_laptop module after the boot. However, this was observed on boot too. If this bug happens on boot, then the keyboard and touchpad may not work, making the netbook unusable until forcefully powered off. This accelerometer can be found on, at least, the Positivo Mobo 5900 and Multilaser MLX5 Educ netbook models. On the Mobo, the accelerometer rarely causes problems (this netbook can be used as a tablet), but on the MLX5 the problems are frequent, requiring to reboot them two or even three times until the netbook's keyboard, touchpad and accelerometer work correctly. While one possible approach would be to blacklist the classmate_laptop module, losing the access to the accelerometer would be a significant problem, at least on the Mobo 5900. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-40-generic 5.3.0-40.32~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 11 14:32:12 2020 InstallationDate: Installed on 2019-11-16 (116 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1867033 Title: Kernel BUG when loading classmate_laptop, accelerometer does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1867033/+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 1865876] [NEW] Errno 5 on installing Ubuntu Studio
Public bug reported: Installing Ubuntu Studio from DVD or Live USB I get Errno 5 and installation crashes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-lowlatency 5.3.1 Uname: Linux 5.3.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Tue Mar 3 14:11:06 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=it_IT.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug eoan third-party-packages ubiquity-19.10.21 ubuntustudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865876 Title: Errno 5 on installing Ubuntu Studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1865876/+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
