[Bug 1974434] Re: Black screen after grub with kernel 5.13.0-41-generic
new lshw with C locale ** Attachment added: "sudo lshw" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+attachment/5591561/+files/lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974434 Title: Black screen after grub with kernel 5.13.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974434] Re: Black screen after grub with kernel 5.13.0-41-generic
** Attachment added: "sudo lshw" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+attachment/5591556/+files/lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974434 Title: Black screen after grub with kernel 5.13.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974434] Re: Black screen after grub with kernel 5.13.0-41-generic
Here the journalctl -k of one machine with the problem (obtained via ssh) ** Attachment added: "journalctl.k.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+attachment/5591554/+files/journalctl.k.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974434 Title: Black screen after grub with kernel 5.13.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974434] Re: Black screen after grub with kernel 5.13.0-41-generic
** Attachment added: "lspci -vv" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+attachment/5591560/+files/lspci-vv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974434 Title: Black screen after grub with kernel 5.13.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974434] [NEW] Black screen after grub with kernel 5.13.0-41-generic
Public bug reported: After updating linux-image-generic-hwe-20.04 to 5.13.0-41-generic, After getting the 5.13.0-41-generic update from the linux-image-generic- hwe-20.04 package, I get a black screen right after the Grub menu is displayed. Selecting the previous kernel in the advanced menu of Grub fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.13.0.41.46~20.04.26 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 20 13:39:30 2022 InstallationDate: Installed on 2017-01-11 (1954 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-09-03 (623 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-01-11T16:59:14.311990 ** Affects: linux-meta-hwe-5.13 (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/1974434 Title: Black screen after grub with kernel 5.13.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.13/+bug/1974434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969968] Re: impressive segfault
Third try on a computer with Intel graphical card (the first two was AMD powered), with ubuntu live session. Same core dump crash. Fun fact, the "demo.pdf" given with the package have "no page" :D Welcome to Impressive version 0.13.0-beta2 (SVN r298) pygame 2.1.2 (SDL 2.0.20, Python 3.10.4) Hello from the pygame community. https://www.pygame.org/contribute.html Detected screen size: 1920x1080 pixels PDF renderer: Xpdf/Poppler pdftkParse() FAILED WARNING: The input file `/usr/share/doc/impressive/demo.pdf' could not be analyzed. The presentation doesn't have any pages, quitting. With another PDF : Welcome to Impressive version 0.13.0-beta2 (SVN r298) pygame 2.1.2 (SDL 2.0.20, Python 3.10.4) Hello from the pygame community. https://www.pygame.org/contribute.html Detected screen size: 1920x1080 pixels PDF renderer: Xpdf/Poppler pdftkParse() FAILED Erreur de segmentation (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969968 Title: impressive segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/impressive/+bug/1969968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969968] Re: impressive segfault
I have tried on another computer with Wayland or X.org session, and i got the same "core dumped" crash. Output on X.org: Welcome to Impressive version 0.13.0-beta2 (SVN r298) pygame 2.1.2 (SDL 2.0.20, Python 3.10.4) Hello from the pygame community. https://www.pygame.org/contribute.html Detected screen size: 1680x1050 pixels PDF renderer: MuPDF 1.4 or newer pdftkParse() FAILED Erreur de segmentation (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969968 Title: impressive segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/impressive/+bug/1969968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969968] [NEW] impressive segfault
Public bug reported: On Ubuntu 22.04 with default Ubuntu session (Wayland) impressive crash when trying to open any PDF files. Terminal say : Welcome to Impressive version 0.13.0-beta2 (SVN r298) pygame 2.1.2 (SDL 2.0.20, Python 3.10.4) Hello from the pygame community. https://www.pygame.org/contribute.html Detected screen size: 2560x1080 pixels PDF renderer: MuPDF 1.4 or newer Segmentation error Crash happen with or without mupdf installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: impressive 0.13.0~beta2-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 19:15:49 2022 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: impressive UpgradeStatus: Upgraded to jammy on 2022-04-22 (0 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 ** Affects: impressive (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969968 Title: impressive segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/impressive/+bug/1969968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Hello, I just upgraded to 42.0-3ubuntu1 and everything works without workaround. Thanks ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Same for me, I steel need MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to get GDM/Mutter working properly. I attach the result of journalctl -e (during failed session), in case it can be useful ? ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+attachment/5576864/+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/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966808] Re: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument)
MUTTER_DEBUG_USE_KMS_MODIFIERS=0 fixes the issue for me too. I will give a new try without this variable after update 42.0-1ubuntu1 is released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [amdgpu][radeon] gnome-shell Wayland sessions fail to start (Failed to lock front buffer on /dev/dri/card1: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966781] Re: gdm3 refuse to launch
** Attachment added: "journalctl -e" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966781/+attachment/5573823/+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/1966781 Title: gdm3 refuse to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966781] [NEW] gdm3 refuse to launch
Public bug reported: For 2 weeks now, my test machine for ubuntu next boot to black screen with only the white cursor in top left corner. journalctl -e show many gnome-shell error complaining about : /dev/dri/card0 error, the computer run with an AMD FirePro W5000 (Pitcairn LE GL) I found some Internal Error : could not resolve keysym: XF86... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 28 17:01:44 2022 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2020-06-09 (657 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966781 Title: gdm3 refuse to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922884] Re: transmission-gtk segfault (core dumped)
I found nothing in /var/crash but in step 2 here the link : https://errors.ubuntu.com/oops/4d63d2e6-9775-11eb-96c2-fa163ee63de6 Now the machine has been upgraded to Impish but transmission always crash. So I got a crash file but when I try : ubuntu-bug /var/crash/_usr_bin_transmission-gtk.1000.crash I click on "Send" in the popup nd... nothing. :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922884 Title: transmission-gtk segfault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1922884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
I tried the new kernel 5.11.0-36-generic, but the problem is still there. I'm attaching the log in case it's helpful. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5526932/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
Sorry for the wait, I took a few days off. This kernel worked well. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5525012/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
Result: partial freeze of the screens. No mouse but keyboard ok. htop running but unable to launch a new prompt or any other process. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5523256/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
This time, GDM failed to launch (without dock). I ended the startup sequence on a blinking cursor in the upper left corner and that was it. I was able to connect to the TTY2 where I ran htop. There I plugged the dock and a kernel oops was displayed. Then, htop progressively erased it partially. From there, impossible to start a new session. I also quit htop but I didn't get the prompt back. Note: a little problem during the installation, I added the dpkg log at the beginning of the attachment file. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5522801/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
And here is the result: complete freeze of the screens. I attached the logs as usual. So 5.14.0-rc2 works and 5.13.13 crash. It remains to find what has been corrected between these two versions? ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5522140/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
There are no deb packages in the first link (rc1). The rc2 version started and worked without problem with the dock and the two screens. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5521666/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
I booted the kernel 5.13.12 with the dock unplugged, everything went well. Once the dock was plugged in, the screen froze but strangely this time, I could move the mouse on the screen (with the trackpad of the laptop). Maybe I didn't notice this possibility before? I then started the kernel 5.14.rc3 and everything worked fine, even with the dock plugged in. You will find the logs attached. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5521252/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
You're welcome. Thank you for taking time to solve this problem! The result was close to the previous version 5.13: The boot with dock and dual screen crashed at 4s then, after a dozen seconds, a kernel dump was displayed, then nothing. The startup without the dock went well, then the connection of the dock again caused a partial blocking and an inability to start a new process. Attached, the log of journalctl. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520701/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
@Chris Chiu (mschiu77): "So the mainline 5.14 works for you even with 2 monitors connected, right?" → Yes ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
I just tested both kernels and here are the results: I first rebooted on the 5.11.0-33 kernel with the dock and the two screens connected. The system froze after 3s of boot. I unplugged the dock and rebooted on the 5.11.0-33 kernel. The boot went well until the desktop. There, I reconnected the dock and everything froze. I then tried the 5.13.0-14 kernel, dock unplugged. The boot went well until the desktop. There, I plugged the dock again and the system partially froze. The mouse didn't move anymore, but I could still manipulate the Gnome 3 shell with the keyboard. I wanted to launch a terminal, the window opened but the shell (bash) failed to initialize (no prompt). I had to produce a hard reboot of the computer. I finally retried the kernel 5.13.0-14, dock connected. The startup slowed down progressively until Systemd showed me a list of pending services... Attached, the corresponding logs that journalctl managed to store (2 out of 4 attempts). It seems that these are the ones where I plugged the dock in a second time. ** Attachment added: "journalctl-k.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520450/+files/journalctl-k.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
@Chris Chiu (mschiu77): "And does it only happen 100% when 2 monitors connected?" → Yes ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
Ok, sorry, I went a little too fast! The attachment #23 does not contain the right log. Apologize. Fortunately, attachment #25 contains interesting items. Look for the sequence "-- Reboot --" and there, at occurrence #54 and #55, there seems to be traces of kernel panic. There are also two boot sequences logs of kernel 5.14 at occurrence #70 and #71. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
If it helps, I also post the result of `journalctl -k -b all` here. I have the impression that the kernel panic of kernel 5.11 does not appear, the crash occurs systematically between seconds 2 and 4 of the boot sequence. However, this extraction contains logs of successful boot on kernel 5.11, when the dock is not connected. Hoping that could be useful... ** Attachment added: "journalctl -k -b all (7z compressed)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520114/+files/journalctl-k-b_all.7z -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
** Attachment added: "dpkg -i *5.14*.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520109/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
5.14.0-rc7 boot without problem even if the dock and the two additional screen are plugged in. I put the boot log in attachment ** Attachment added: "journalctl -k -b -1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5520108/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
Ok, but I don't know how to "take a snapshot" while my machine run into a kernel panic. Can you explain me how to do that ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518159/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518161/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518160/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518155/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518158/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518157/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518154/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518156/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518152/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518153/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518150/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518147/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518151/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518149/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518148/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518146/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
apport information ** Tags added: apport-collected focal ** Description changed: Hello, My laptop run well with last 5.4 linux kernel even if I connect my thunderbolt dock. When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock and 2 monitors connected, the kernel panic after 3 or 4 seconds. Without the dock, he work fine. - After a lot of try, I was able to boot sometime on 5.11 with the dock, - but randomly and only if I only connect 1 extra monitor (I usually use - two). + After a lot of try, I was able to boot sometime on 5.11 with the dock, but randomly and only if I only connect 1 extra monitor (I usually use two). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jmaillar 1988 F pulseaudio + /dev/snd/controlC1: jmaillar 1988 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=none + MachineType: Dell Inc. Precision 7530 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro + ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-27-generic N/A + linux-backports-modules-5.11.0-27-generic N/A + linux-firmware 1.187.15 + Tags: focal + Uname: Linux 5.11.0-27-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago) + UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers video wireshark + _MarkForUpload: True + dmi.bios.date: 05/25/2021 + dmi.bios.release: 1.16 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.16.1 + dmi.board.name: 0425K7 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Precision + dmi.product.name: Precision 7530 + dmi.product.sku: 0831 + dmi.sys.vendor: Dell Inc. + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 + mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518144/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1940113/+attachment/5518145/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
** Attachment added: "journalctl -k -b -1 > journal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5518125/+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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940113] [NEW] Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
Public bug reported: Hello, My laptop run well with last 5.4 linux kernel even if I connect my thunderbolt dock. When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock and 2 monitors connected, the kernel panic after 3 or 4 seconds. Without the dock, he work fine. After a lot of try, I was able to boot sometime on 5.11 with the dock, but randomly and only if I only connect 1 extra monitor (I usually use two). ** 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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922884] [NEW] transmission-gtk segfault (core dumped)
Public bug reported: Unable to launch transmission-gtk application, segfault. Ubuntu 21.04 up-to-date. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: transmission-gtk 3.00-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 09:47:02 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to hirsute on 2020-06-09 (301 days ago) ** Affects: transmission (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1922884 Title: transmission-gtk segfault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1922884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I haven't noticed the intel-microcode update of 2020/12/11 Know, with intel-microcode 3.20201110.0ubuntu0.20.04.2 focal package, my computer start normally and without any tweak ! Greaaat ! Thanks a lot to anybody make it happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
I haven't noticed the intel-microcode update of 2020/12/11 Know, with intel-microcode 3.20201110.0ubuntu0.20.04.2 focal package, my computer start normally and without any tweak ! Greaaat ! Thanks a lot to anybody make it happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
It will soon be 1 year since my laptop can no longer boot without power supply if I use an official version of Ubuntu. This bug is marked "incomplete" without ever having been informed of what is missing... This is very frustrating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897712] [NEW] Ugly image output make game unusable
Public bug reported: Start a new game, the jewel is replaced by ugly "graphical buffer noise". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gweled 0.9.1-7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:47:30 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gweled UpgradeStatus: Upgraded to groovy on 2020-06-09 (112 days ago) ** Affects: gweled (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897712 Title: Ugly image output make game unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gweled/+bug/1897712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
I have received the updated package intel-microcode 3.20200609.0ubuntu0.20.04.2. I still have the same problem. Without power supply the boot hang at ramdisk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I have received the updated package intel-microcode 3.20200609.0ubuntu0.20.04.2. I still have the same problem. Without power supply the boot hang at ramdisk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I've been trying to disable SGX myself. But it didn't help. It's been almost a year since my laptop stopped booting up without a power supply. It's extremely frustrating and annoying! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
Incomplete ? What's missing ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
Have updated my laptop to Ubuntu 20.04. Problem still here... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
Have updated my laptop to Ubuntu 20.04. Problem still here... ** This bug is no longer a duplicate of bug 1862751 Hard lockups using microcode releases 20191115 on Intel Whiskey Lake -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865457] [NEW] gedit tango color scheme display ugly white grid pattern
Public bug reported: - launch gedit - in the three lines "burger" menu, select "Preferences" - in "View" tab, activate "Display grid pattern" option - in "Font & Colors" tab, select "/* Tango */" >From now on, a uggly white grid covers the surface of the editing area. Shouldn't this dark theme display a dark grid as well ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 2 11:09:04 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2018-11-14 (473 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot_2020-03-02_11-20-56.png" https://bugs.launchpad.net/bugs/1865457/+attachment/5332680/+files/screenshot_2020-03-02_11-20-56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865457 Title: gedit tango color scheme display ugly white grid pattern To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1865457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
@vicamo, sorry for the delay, I had some apprehension playing with the microcode of my workstation and I had an important class to give yesterday ... In short, yippee, the first successful start without a power source in months. Thank you! I guess I'll have to remove this PPA at the next official update of the intel-microcode package? Many thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
@vicamo, I attach the informations $(dmesg | grep microcode) give me when booting with power supply and no special kernel option, and some other potentially useful info. I'm not sure this is what you asked me to give you :-/ Know, I don't understand why the result of dmesg command is different from the result obtained after starting on battery with the nosmp option that you linked in the message #3. thank you for your involvement! ** Attachment added: "dmesg | grep microcode, uname, os-release, ..." https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+attachment/5327902/+files/dmesg-microcode-uname-os-release ** Changed in: intel-microcode (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
@vicamo, "system just hangs unless manually powered off. Is this correct?": Yes ! 1. It's work ! 2. Yes, I attach the result ** Attachment added: "dmesg | grep microcode" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853369/+attachment/5327645/+files/dmesg-microcode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
@vicamo I tried your boot parameters, I'm attaching photos of the boot sequence in a zip file. I don't understand why booting work when "power" is connected (2 thunderbolt dock or notebook charger) and not when on battery. ** Attachment added: "boot sequence photos" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853369/+attachment/5327640/+files/sequence.7z -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I'm running 19.10 with linux package 5.3.0-29.31 ... problem still here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859411] [NEW] package fonts-noto-core 20200103-1 failed to install/upgrade: tentative de remplacement de « /usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appartient aussi au paq
Public bug reported: Error reported after upgrading my test machine ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-noto-core 20200103-1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Fri Jan 10 09:30:56 2020 Dependencies: ErrorMessage: tentative de remplacement de « /usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appartient aussi au paquet fonts-noto-unhinted 20181227-1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.5 SourcePackage: fonts-noto Title: package fonts-noto-core 20200103-1 failed to install/upgrade: tentative de remplacement de « /usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appartient aussi au paquet fonts-noto-unhinted 20181227-1 UpgradeStatus: Upgraded to focal on 2018-11-14 (424 days ago) ** Affects: fonts-noto (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/1859411 Title: package fonts-noto-core 20200103-1 failed to install/upgrade: tentative de remplacement de « /usr/share/fonts/truetype/noto /NotoSansJavanese-Bold.ttf », qui appartient aussi au paquet fonts- noto-unhinted 20181227-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1859411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] [NEW] [19.10] Boot hangs at "loading initial ramdisk"
*** This bug is a duplicate of bug 1853369 *** https://bugs.launchpad.net/bugs/1853369 Public bug reported: My laptop hangs on "loading initial ramdisk" at startup. However, it start up without any problems when the power supply is connected 0_o … ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmaillar 2529 F pulseaudio /dev/snd/controlC1: jmaillar 2529 F pulseaudio CurrentDesktop: GNOME Date: Wed Jan 8 16:22:21 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=none MachineType: Dell Inc. Precision 7530 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro tpm_tis.interrupts=0 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-22 (78 days ago) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0425K7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd11/11/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0831 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** This bug has been marked a duplicate of bug 1853369 [19.10] Boot hangs at "loading initial ramdisk" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
You can find my data here : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858810 Ask me anything that'll help. ** 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
I am also affected My laptop hangs on "loading initial ramdisk" at startup. However, it start up without any problems when the power supply is connected 0_o … -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Hello Adam, My test machine has been migrated to Focal. I don't know if this can help, however, the bug has disappeared with the Focal versions of grub/shim. Ask me for command outputs if necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
I noticed in the attached document of comment #18 that some files were missing: grub-install: info: cannot open `/usr/lib/shim/shim/fbx64.efi': No such file or directory. grub-install: info: cannot open `/usr/lib/shim/mmx64.efi': No such file or directory. Because these files come from the "shim" package, I installed it. Then, I restarted "grub-install" but it didn't have any effect, Windows still refuses to boot from Grub. Is it normal that the shim package is not a dependency of grub-efi- amd64-signed? ** Changed in: grub2 (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/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
@cyphermox I have executed the commands as indicated. I reinstalled grub-efi-amd64 and grub-efi-amd64-signed and ran grub-install -v. You will find the results of the commands in the attached file. Windows still refuses to boot from Grub. ** Attachment added: "Commands output" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+attachment/5299097/+files/commands-output.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Is that a duplicate of https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317 ? ** Changed in: grub2 (Ubuntu Eoan) 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/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Here the details of /boot file (with EFI partition mounted) ** Attachment added: "find /boot output (with EFI partition mounted)" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+attachment/5297817/+files/find_in_boot_dir.output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Yes, by using the F12 key, I can display the EFI start menu and start Windows with the "Windows Boot Manager" line. This is a test machine that follows the development of "Ubuntu next". Initially installed with Ubuntu 17.10 beta, it has followed the updates of all Ubuntu development versions (18.04, 18.10, ...) until today. Now in 19.10, it will soon switch to Ubuntu Focal 20.04). The Windows part has been re-installed from scratch with an Windows 10 18.03 USB flash drive installer and regularly updated. Now running W10-19.03. After installing Windows, Grub was re-installed by starting the machine with Ubuntu-Live 18.04 and then entering the following commands: $ sudo mount /dev/sda2 /mnt $ for i in dev sys proc dev/pts; do sudo mount -o bind /$i /mnt/$i; done $ sudo chroot /mnt # apt purge grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common # apt install grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common # update-grub (... reboot → Ubuntu ...) $ sudo update-grub Everything was working well until more or less half-time of 19.10 developpement. Here my partitioning : $ sudo parted /dev/sda print Model: ATA M4-CT512M4SSD2 (scsi) Disk /dev/sda: 512GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 1049kB 1075MB 1074MB fat32esp boot, esp 2 1075MB 207GB 206GB ext4 Ubuntu 3 207GB 345GB 137GB ntfs data msftdata 4 345GB 345GB 16.8MB Microsoft reserved partition msftres 5 345GB 512GB 167GB ntfs Basic data partition msftdata 6 512GB 512GB 520MB ntfs hidden, diag -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] [NEW] Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
Public bug reported: On a dual boot computer with Windows 10 Pro and Ubuntu 19.10, since a month, Grub was unable to boot Windows 10. Hitting the Windows entry line give me a 0.1s black screen and get me back to Grub Menu. sudo update-grub give me : Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.3.0-10-generic Found initrd image: /boot/initrd.img-5.3.0-10-generic Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub-efi-amd64 2.04-1ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 08:01:05 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: grub2 UpgradeStatus: Upgraded to eoan on 2018-11-14 (314 days ago) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "/boot/grub/grub.cfg" https://bugs.launchpad.net/bugs/1845289/+attachment/5291052/+files/grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824765] [NEW] freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED
Public bug reported: When I try to initiate a rdp:// connexion, gnome-boxes freeze during the login entry before I hit the enter key. Here the terminal output : [09:35:44:478] [9818:9913] [WARN][com.winpr.sspi] - InitializeSecurityContextA status SEC_E_OUT_OF_SEQUENCE [0x80090310] [09:35:44:480] [9818:9913] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F] [09:35:44:481] [9818:9913] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error [09:35:44:495] [9818:9913] [WARN][com.winpr.sspi] - InitializeSecurityContextA status SEC_E_OUT_OF_SEQUENCE [0x80090310] [09:35:44:497] [9818:9913] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F] [09:35:44:498] [9818:9913] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error (…last 3 lines repeated 133 times…) [09:35:47:876] [9818:9913] [WARN][com.winpr.sspi] - InitializeSecurityContextA status SEC_E_OUT_OF_SEQUENCE [0x80090310] [09:35:47:878] [9818:9913] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F] [09:35:47:878] [9818:9913] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error [09:35:47:893] [9818:9913] [WARN][com.winpr.sspi] - InitializeSecurityContextA status SEC_E_OUT_OF_SEQUENCE [0x80090310] [09:35:47:895] [9818:9913] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F] [09:35:47:895] [9818:9913] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error [09:35:47:897] [9818:9913] [ERROR][com.winpr.thread] - failed to create thread pipe fd 0 [09:35:47:897] [9818:9913] [ERROR][com.freerdp.core.codecs] - Failed to create rfx codec context Erreur de segmentation (core dumped) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-boxes 3.32.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:36:12 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-boxes UpgradeStatus: Upgraded to disco on 2018-11-14 (151 days ago) ** Affects: gnome-boxes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1824765 Title: freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1824765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822059] Re: Wrong font in GIMP user interface
Obviously, this is a problem with Gtk2 applications (see WinFF screenshot) ** Attachment added: "WinFF screenshot" https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1822059/+attachment/5250107/+files/winff.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822059 Title: Wrong font in GIMP user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1822059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822059] [NEW] Wrong font in GIMP user interface
Public bug reported: On an updated Ubuntu Disco, Gimp does not use the font configured in Gnome-Tweaks. I chose "Ubuntu Condensed Regular" font for the "Interface text". Gimp displays a completely different font with serifs (See attached screenshot). I also tested the "flathub" version of Gimp (flatpak install flathub org.gimp.GIMP). It has the same problem. Gtk2 support broken ? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gimp 2.10.8-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 10:03:04 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to disco on 2018-11-14 (133 days ago) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1822059/+attachment/5250101/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202019-03-28%2010-15-39.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822059 Title: Wrong font in GIMP user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1822059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821301] Re: Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio: A_OPUS)
** Attachment added: "English localised mkvinfo of the played video file" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1821301/+attachment/5248401/+files/mkvinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821301 Title: Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio: A_OPUS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1821301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821301] [NEW] Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio: A_OPUS)
Public bug reported: I try to read a video with totem, I heard some digital noise (less than one second) and only see a black screen. Nothing append after that, totem UI work but the video file don't play. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.2-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 09:48:13 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to disco on 2018-11-14 (127 days ago) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Attachment added: "mkvinfo of the played file" https://bugs.launchpad.net/bugs/1821301/+attachment/5248396/+files/mkvinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821301 Title: Totem was unable to read a mkv file (video: V_MPEG4/ISO/AVC, audio: A_OPUS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1821301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816013] [NEW] gnome-taquin don't start and eat 100% of a processing core
Public bug reported: Trying to launch gnome-taquin on a freshly upgraded Disco but only obtain a core working at 100% and need a ctrl+c to stop it. I attach logs from --gtk-debug=all ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-taquin 3.31.90-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 09:15:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-taquin UpgradeStatus: Upgraded to disco on 2018-11-14 (92 days ago) ** Affects: gnome-taquin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Attachment added: "gtk-debug-all logs" https://bugs.launchpad.net/bugs/1816013/+attachment/5238830/+files/gnome-taquin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816013 Title: gnome-taquin don't start and eat 100% of a processing core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-taquin/+bug/1816013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812348] [NEW] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927
Public bug reported: Each time I boot my laptop (and time to time after), the log show this crash : [ 47.202056] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:927 [ 47.202109] WARNING: CPU: 5 PID: 868 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:254 generic_reg_wait+0xe4/0x160 [amdgpu] [ 47.202110] Modules linked in: ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter snd_hrtimer bnep nfnetlink_log nfnetlink zram binfmt_misc nls_iso8859_1 arc4 dell_smm_hwmon cdc_ether usbnet joydev r8152 mii dell_rbtn intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_usb_audio snd_usbmidi_lib razerkbd(OE) aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf iwlmvm dell_laptop mac80211 snd_hda_codec_realtek snd_hda_codec_generic input_leds serio_raw snd_hda_codec_hdmi [ 47.202131] dell_wmi dell_smbios dcdbas iwlwifi snd_hda_intel snd_hda_codec btusb dell_wmi_descriptor btrtl uvcvideo btbcm snd_hda_core btintel snd_hwdep bluetooth videobuf2_vmalloc ecdh_generic snd_seq_midi videobuf2_memops intel_wmi_thunderbolt wmi_bmof snd_seq_midi_event snd_pcm videobuf2_v4l2 videobuf2_common videodev media cfg80211 snd_rawmidi rtsx_pci_ms memstick snd_seq snd_seq_device snd_timer hid_multitouch mei_me idma64 mei virt_dma snd processor_thermal_device ucsi_acpi soundcore typec_ucsi intel_pch_thermal intel_soc_dts_iosf typec int3403_thermal int340x_thermal_zone dell_smo8800 int3400_thermal intel_hid acpi_thermal_rel sparse_keymap acpi_pad mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic amdkfd [ 47.202150] amd_iommu_v2 amdgpu rtsx_pci_sdmmc chash gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops i2c_i801 thunderbolt nvme drm i2c_hid rtsx_pci ahci intel_lpss_pci nvme_core libahci intel_lpss hid wmi pinctrl_cannonlake video pinctrl_intel [ 47.202161] CPU: 5 PID: 868 Comm: kworker/5:4 Tainted: GW OE 4.18.0-13-generic #14-Ubuntu [ 47.202161] Hardware name: Dell Inc. Precision 7530/0425K7, BIOS 1.5.2 11/01/2018 [ 47.202170] Workqueue: events drm_mode_rmfb_work_fn [drm] [ 47.202195] RIP: 0010:generic_reg_wait+0xe4/0x160 [amdgpu] [ 47.202195] Code: a9 44 8b 45 20 48 8b 4d 18 89 de 44 89 4d d4 8b 55 10 48 c7 c7 10 74 74 c0 e8 48 47 d4 ff 41 83 7c 24 20 01 44 8b 4d d4 74 02 <0f> 0b 48 83 c4 18 44 89 c8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 41 0f [ 47.202210] RSP: 0018:b7df44a9f948 EFLAGS: 00010297 [ 47.202211] RAX: RBX: 000a RCX: [ 47.202211] RDX: RSI: 8c801bd564b8 RDI: 8c801bd564b8 [ 47.202212] RBP: b7df44a9f988 R08: 00031548 R09: 00010200 [ 47.202212] R10: 0004 R11: a2f8480d R12: 8c7feb1b7300 [ 47.202213] R13: 0bb9 R14: 0001 R15: [ 47.202214] FS: () GS:8c801bd4() knlGS: [ 47.202214] CS: 0010 DS: ES: CR0: 80050033 [ 47.202215] CR2: 7f72dc02d3c8 CR3: 00058040a002 CR4: 003606e0 [ 47.202216] DR0: DR1: DR2: [ 47.202216] DR3: DR6: fffe0ff0 DR7: 0400 [ 47.202216] Call Trace: [ 47.202245] dce110_stream_encoder_dp_blank+0x12f/0x1a0 [amdgpu] [ 47.202269] dce110_blank_stream+0x57/0x90 [amdgpu] [ 47.202293] core_link_disable_stream+0x57/0x220 [amdgpu] [ 47.202317] dce110_reset_hw_ctx_wrap+0xcd/0x1e0 [amdgpu] [ 47.202340] dce110_apply_ctx_to_hw+0x52/0xa30 [amdgpu] [ 47.202364] ? dce110_apply_ctx_for_surface+0x1f2/0x270 [amdgpu] [ 47.202387] dc_commit_state+0x306/0x5b0 [amdgpu] [ 47.202392] ? drm_atomic_helper_setup_commit+0x31e/0x420 [drm_kms_helper] [ 47.202418] amdgpu_dm_atomic_commit_tail+0x37f/0xe40 [amdgpu] [ 47.202421] ? _cond_resched+0x19/0x30 [ 47.202422] ? wait_for_completion_timeout+0x38/0x140 [ 47.202423] ? _cond_resched+0x19/0x30 [ 47.202424] ? wait_for_completion_interruptible+0x35/0x1a0 [ 47.202428] commit_tail+0x42/0x70 [drm_kms_helper] [ 47.202431] drm_atomic_helper_commit+0x113/0x120 [drm_kms_helper] [ 47.202457] amdgpu_dm_atomic_commit+0x87/0xa0 [amdgpu] [ 47.202464] drm_atomic_commit+0x4a/0x50 [drm] [ 47.202470] drm_framebuffer_remove+0x2df/0x3f0 [drm] [ 47.202476] drm_mode_rmfb_work_fn+0x41/0x50 [drm] [ 47.202478] process_one_work+0x20f/0x3c0 [ 47.202480] worker_thread+0x233/0x400 [ 47.202481] kthread+0x120/0x140 [
[Bug 1809564] [NEW] Unfocused tilix window transparency
Public bug reported: With Yaru theme the background transparency of unfocused Tilix Windows is removed. I mean, when a Tilix terminal is focused, the transparency settings is correctly applied to the background. But, if the windows loose the focus, the background became opaque. With other gtk theme like adwaita or arc ... we don't have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gtk 18.10.6 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 23 01:24:28 2018 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809564 Title: Unfocused tilix window transparency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809015] [NEW] mtr-paquet: Failure to open IPv4 sockets: Operation not permitted
Public bug reported: Since I have upgraded my system from 18.04 to 18.10, I was unable to use mtr without root privilege. $ mtr 9.9.9.9 Failure to open IPv4 sockets: Operation not permitted Failure to open IPv6 sockets: Operation not permitted mtr: Failure to start mtr-packet: Invalid argument With sudo, everything work great. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mtr-tiny 0.92-2 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 18 18:15:05 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mtr UpgradeStatus: Upgraded to cosmic on 2018-12-10 (8 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 ** Affects: mtr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809015 Title: mtr-paquet: Failure to open IPv4 sockets: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtr/+bug/1809015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768754] Re: Applications are muted (silent) but system sounds work
Has I say in my report : "Graphically, applications react normally, we can see their connections with pulse audio in the applications tab of the sound settings. But no sound comes out of the speakers." At UI level, everything seem to work, application volume is not mutted. The stranger thing is that gnome feedback sound work where application sound (mpv, firefox, ...) don't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768754 Title: Applications are muted (silent) but system sounds work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739476] Re: Scilab 6.0 launches, shows its window and closes immediately on bionic and cosmic
Same problem after 18.04 upgrade. Need to switch "Terminal" parameter to true in desktop file : $ sudo sed -i 's/Terminal=false/Terminal=true/' /usr/share/applications/scilab.desktop Also need to correct the "classpath.xml" file : $ sudo sed -i 's/jlatexmath-fop-1.0.6.jar/jlatexmath-fop-1.0.7.jar/' /usr/share/scilab/etc/classpath.xml And finally need to install libcanberra-gtk to stop scilab complain about its lake : $ sudo apt install libcanberra-gtk-module libcanberra-gtk3-module -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739476 Title: Scilab 6.0 launches, shows its window and closes immediately on bionic and cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1739476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788362] [NEW] Xorg session freeze (radeon stalled)
Public bug reported: Cosmic updated with new xorg packages Login to « Ubuntu » session : show me a screen parasite checkerboard for some second and finally display my desktop, but it was frozen. The second in the clock don't move. every 5 to 10 second the screen go black and came back, but time in clock is at the same position that before screen go black. Sometime, the display go to text terminal and display many line of « radeon stalled for seconds ... ». Login to « Ubuntu on Wayland » work good. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xserver-xorg-video-radeon 1:18.0.1-1build1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Wed Aug 22 10:54:02 2018 DistUpgraded: 2018-05-17 11:46:01,986 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] [1002:675d] (prog-if 00 [VGA controller]) Subsystem: Dell Turks PRO [Radeon HD 7570] [1028:2b20] MachineType: Dell Inc. OptiPlex 390 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-7-generic root=UUID=87f92239-240d-4213-ad2e-2c94b76ead3a ro splash quiet vt.handoff=1 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to cosmic on 2018-05-17 (96 days ago) dmi.bios.date: 10/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0M5DCD dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 390 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.93-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.0-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic has-workaround 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/1788362 Title: Xorg session freeze (radeon stalled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1788362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782606] [NEW] 18.10 : Tilix symbol lookup error
Public bug reported: 18.10 up-to-date tilix 1.7.9-2ubuntu1 amd64 tilix-common 1.7.9-2ubuntu1 all Running tilix : $ tilix tilix: symbol lookup error: tilix: undefined symbol: _D4glib3StrQe9toStringzFAyaZPa ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: tilix 1.7.9-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 19 18:06:40 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: tilix UpgradeStatus: Upgraded to cosmic on 2018-05-17 (63 days ago) ** Affects: tilix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782606 Title: 18.10 : Tilix symbol lookup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1782606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756594] Re: Tilix symbol lookup error
Ok, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756594 Title: Tilix symbol lookup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1756594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756594] Re: Tilix symbol lookup error
18.10 up-to-date tilix1.7.9-2ubuntu1 amd64 tilix-common 1.7.9-2ubuntu1 all Running tilix : $ tilix tilix: symbol lookup error: tilix: undefined symbol: _D4glib3StrQe9toStringzFAyaZPa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756594 Title: Tilix symbol lookup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1756594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775351] [NEW] Dolphin loose game-controller configuration after game launch
Public bug reported: Reproducing : Launch dolphin emulator and use controllers panel to configure your gamepad as controller. After configuring everything, gamepad seem to work correctly with the configuration panel indicators. Close panel, re- open it, indicators always work. Launch any game emulation, the controllers doesn't work. Return to the configuration panel, controllers seem not configured at all. Tested on fresh Bionic and fresh Cosmic. Workaround : Launch a game than, while the game work, configure your gamepad and return to the live game. It's work until you launch any other game. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dolphin-emu 5.0+dfsg-2build1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 6 09:56:29 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: dolphin-emu UpgradeStatus: Upgraded to bionic on 2018-04-24 (43 days ago) ** Affects: dolphin-emu (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/1775351 Title: Dolphin loose game-controller configuration after game launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin-emu/+bug/1775351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771359] Re: No matching cipher found even if client and server have matching cipher
It's not a bug ! ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/openssh/+question/669164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771359 Title: No matching cipher found even if client and server have matching cipher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771359] Re: No matching cipher found even if client and server have matching cipher
Thank you for your reply. I'm sorry, I did not think about watching the ChangeLog. Indeed, it is not a bug, it may be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771359 Title: No matching cipher found even if client and server have matching cipher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771359] [NEW] No matching cipher found even if client and server have matching cipher
Public bug reported: Since Bionic upgrade (from Artful) I encounter problem to call HP switch with SSH. After the upgrade, trying to ssh some switch give me this message : $ ssh 192.168.0.1 Unable to negotiate with 192.168.0.1 port 22: no matching cipher found. Their offer: aes128-cbc,3des-cbc,des-cbc So, I look for supported cipher : $ ssh -Q cipher 3des-cbc aes128-cbc aes192-cbc aes256-cbc rijndael-...@lysator.liu.se aes128-ctr aes192-ctr aes256-ctr aes128-...@openssh.com aes256-...@openssh.com chacha20-poly1...@openssh.com I see that aes128-cbc seem both supported. So I try... : $ ssh -c aes128-cbc 192.168.0.1 ...and It's work ! Workaround : I've added “ciphers aes128-cbc” to ~/.ssh/config file for each switch I manage. The ssh-client should detect automatically the good cipher ? No ? Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue May 15 15:39:00 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:7.6p1-4 SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-24 (21 days ago) ** Affects: openssh (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/1771359 Title: No matching cipher found even if client and server have matching cipher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768766] Re: Display monitor randomly switch to “economy mode” during boot sequence and/or login sequence
Sorry, I forgot to give my workaround : * Turn off the monitor (electrically), disconnect the power cord if need... * Turn back on the monitor. * There you go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768766 Title: Display monitor randomly switch to “economy mode” during boot sequence and/or login sequence To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1768766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768766] [NEW] Display monitor randomly switch to “economy mode” during boot sequence and/or login sequence
Public bug reported: When my laptop start on a dock with lid closed and with 2 monitors connected, one DVI and one DisplayPort, sometime, one of the monitors switch to “economy mode” and turn off, randomly. * Sometime, it's happen during boot sequence, when text flow is displayed (yes, I remove “quiet splash” in /etc/default/grub). * Sometime, it's happen on login screen. When it's the bad one, I can't see the login form. * Sometime, it's happen after login, when the desktop is loading. * And some other time, on lucky day, it's not happen at all ! Please, give me instruction to found where the problem come from ? It's really annoying. Thanks for attentions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libdrm-amdgpu1 2.4.91-2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu May 3 10:06:08 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libdrm-common 2.4.91-2 libdrm2 2.4.91-2 libgcc1 1:8-20180414-1ubuntu2 DistUpgraded: 2018-04-24 09:45:14,351 DEBUG /openCache(), new cache size 90810 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: openrazer-driver, 1.0.0, 4.15.0-19-generic, x86_64: installed openrazer-driver, 1.0.0, 4.15.0-20-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X] [1002:6821] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Venus XT [Radeon HD 8870M / R9 M270X/M370X] [103c:2254] MachineType: Hewlett-Packard HP ZBook 15 G2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=79ab29f5-d9eb-4aff-bfb8-8639c60401cb ro SourcePackage: libdrm UpgradeStatus: Upgraded to bionic on 2018-04-24 (9 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.15 dmi.board.name: 2253 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.asset.tag: CND54722DC dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3009CD10002:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N dmi.product.name: HP ZBook 15 G2 dmi.product.version: A3009CD10002 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768766 Title: Display monitor randomly switch to “economy mode” during boot sequence and/or login sequence To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1768766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768754] [NEW] Applications are muted (silent) but system sounds work
Public bug reported: How to reproduce this bug: * Connect a laptop to a dock, which is connected to a screen with an HDMI / DisplayPort cable. * Then configure the sound to exit through the cable connecting the screen. * Turn off the computer * Take it out of the dock * Turn on the computer Then, the sound automatically switches to the audio output of the laptop. System sounds work well, such as the bell of output volume slider or the test speaker buttons “front left” or “front right”. Unfortunately, no more applications can produce a sound. Graphically, applications react normally, we can see their connections with pulse audio in the applications tab of the sound settings. But no sound comes out of the speakers. Workaround : * Connect an alternative audio output, such as a Bluetooth headset * Select it in the “Choose a device for sound output:” option * Switch back to the internal audio speakers * Et voilà ! If it help, my laptop is a “HP Zbook G2” sometime connected to a “HP 2012 230W Docking Station” Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 3 09:21:01 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-04-24 (8 days ago) ** Affects: gnome-control-center (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/1768754 Title: Applications are muted (silent) but system sounds work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
