[Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
And the *release* version of Jammy has a 5.15 kernel that boots on the machine in question, so I've managed a successful upgrade, and this doesn't seem to be a problem for me any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
Update: linux-image-5.14.0-1034-oem appeared in my normal apt upgrade today and has booted successfully, so perhaps whatever the problem was has been fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
This also happens with the kernel in xubuntu-22.04-beta-desktop- amd64.iso, so it will block me upgrading that machine to Jammy when it's released. Is there anything I can do to help? I'm not familiar with debugging kernel drivers, but I'm a competent general developer, and I'm prepared to put in some effort if given some guidance on where to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
I don't really know what information I should be reporting about my hardware. My first guess is that the output of 'lspci -v' relating to the video device might be useful, so here it is: 00:02.0 VGA compatible controller: Intel Corporation Device 4c8a (rev 04) (prog- if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: ASUSTeK Computer Inc. Device 8694 Flags: bus master, fast devsel, latency 0, IRQ 145 Memory at 60 (64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
** Attachment added: "dmesg.nomodeset.5.14.0-1031-oem.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574751/+files/dmesg.nomodeset.5.14.0-1031-oem.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
** Attachment added: "dmesg.success.5.11.0-46-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574752/+files/dmesg.success.5.11.0-46-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967123] [NEW] Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'
Public bug reported: I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has been working fine for me (and supported the network device on my reasonably recent PC, which 20.04's default kernel didn't). But the 5.13 and 5.14 kernels all hang on boot. If I edit the GRUB boot commands to let me see the boot messages, the hang occurs immediately after printing the message [1.044456] fb0: switching to inteldrmfb from EFI VGA I can boot this kernel fine if I add 'nomodeset' to the kernel command line. But then I get unusably low screen resolution. Instead, my workaround is to manually select a 5.11 kernel from the GRUB menu on every boot. I'm not able to provide a full set of kernel messages from a failed boot attempt, because of course the kernel doesn't boot to a point where I can save them to a file. But I attach a screenshot of the last screenful of messages before the hang, in case those are useful. I'll also attach dmesg logs from a successful boot of the 5.14 kernel with nomodeset, and from a boot of the 5.11 kernel which gives me full functionality. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 30 12:47:47 2022 InstallationDate: Installed on 2013-06-01 (3223 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312 ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "kernelcrash.jpeg" https://bugs.launchpad.net/bugs/1967123/+attachment/5574747/+files/kernelcrash.jpeg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967123 Title: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967122] [NEW] Buffer overflow in alsa_card_detect causes linphone to crash at startup
Public bug reported: Linphone crashes at startup for me, if too many audio devices are connected, with a message on stderr saying free(): double free detected in tcache 2 SIGABRT / SIGIOT: Aborted I debugged the problem and found that the crash was occurring in the libmediastreamer_voip.so.10 shared library. Specifically, in src/audiofilters/alsa.c alsa_card_detect(), the arrays card_names[] and device_names[] were being overrun, because they have size MAX_NUM_DEVICE_ID = 100 and there's no overflow check in the code. So one array was overrunning into the other one, causing the double-free when both arrays full of allocated things were cleaned up at the end of the function. (I don't have 100 audio devices! But ALSA reports multiple records for each one, with various different details. I found that with HDMI audio output, USB speakers, and a webcam with microphone, the array overrun occurs; disconnecting the webcam allows Linphone to start up, but then of course I can't use it to make calls.) I've worked around the problem locally by installing a recompiled version of the libmediastreamer-voip10 package in which I reset MAX_NUM_DEVICE_ID from 100 to 1000. With that change, Linphone runs fine and can make calls using my webcam microphone. (My fix is a bodge, of course! A proper fix would enlarge the arrays as needed. But I know that the affected function has been completely rewritten in later versions of mediastreamer2, and those later versions are already in later Ubuntu releases. So I only need that workaround until I can upgrade from 20.04 to 22.04 next month.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libmediastreamer-voip10 1:2.16.1-4ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Mar 30 12:35:18 2022 InstallationDate: Installed on 2013-06-01 (3223 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: mediastreamer2 UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312 ** Affects: mediastreamer2 (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/1967122 Title: Buffer overflow in alsa_card_detect causes linphone to crash at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediastreamer2/+bug/1967122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876212] Re: audacity (with libwxgtk3.0-gtk3) doesn't draw with GTK_IM_MODULE=xim
I've also had this problem with Audacity since updating from 18.04 to 20.04, and indeed, removing GTK_IM_MODULE=xim from the environment worked around it. However, that's not a great workaround for me, because I put that in the environment on purpose. Without it, GTK2 applications don't honour the list of custom compose-key sequences I put in ~/.XCompose. (But GTK3 applications seem to manage without it, so perhaps this will become less of a problem as everything gradually migrates to GTK3.) The interesting thing is that the same bug affects the plot window in gnuplot, at least using the default gnuplot terminal type 'wxt'. So I think it might not be a bug in Audacity itself, but a general bug in the GTK3 backend of wxWindows? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876212 Title: audacity (with libwxgtk3.0-gtk3) doesn't draw with GTK_IM_MODULE=xim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wxwidgets3.0/+bug/1876212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898858] Re: xfce4-notifyd fails to start on displays other than :0
Now I think about it harder, I suppose I should mention a few more details. On the test VM I spun up for the reproducer, I was doing all of this by logging in on a text virtual console. On the real machine where I had this problem originally, I'm doing remote working by SSHing in, running vncserver to start up the X session, and then connecting a VNC client to it. So, in both cases, the user-level systemd process is already running *before* I set up the new X display. I wouldn't be surprised if that was a key part of the problem: if you logged in on a display other than :0 via a normal display manager, it might well have set DISPLAY before even starting "systemd --user", and then everything might work. (But I haven't tried it.) Also, when I say "vncserver", that's the one from the "vnc4server" package. (I think that is probably not critical to the behaviour, but just in case.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898858 Title: xfce4-notifyd fails to start on displays other than :0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1898858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898858] [NEW] xfce4-notifyd fails to start on displays other than :0
Public bug reported: I work remotely by running an XFCE session inside an X display created by vnc4server. On Ubuntu xenial, this causes xfce4-notifyd to fail to start up. A transcript of my VNC startup script and the results: simon@xenial:~$ cat ~/.vnc/xstartup #!/bin/sh exec setsid xfce4-session simon@xenial:~$ vncserver :1 New 'xenial:1 (simon)' desktop is xenial:1 Starting applications specified in /home/simon/.vnc/xstartup Log file is /home/simon/.vnc/xenial:1.log simon@xenial:~$ ps xf | grep xfce4-notifyd 4017 pts/0S+ 0:00 \_ grep --color=auto xfce4-notifyd simon@xenial:~$ systemctl --user status xfce4-notifyd.service ● xfce4-notifyd.service - XFCE notifications service Loaded: loaded (/usr/lib/systemd/user/xfce4-notifyd.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-10-07 11:29:41 BST; 27s ago Process: 3943 ExecStart=/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd (code=exited, status Main PID: 3943 (code=exited, status=1/FAILURE) Oct 07 11:29:41 xenial systemd[3794]: Starting XFCE notifications service... Oct 07 11:29:41 xenial xfce4-notifyd[3943]: Unable to init server: Could not connect: Connection ref Oct 07 11:29:41 xenial xfce4-notifyd[3943]: cannot open display: Oct 07 11:29:41 xenial systemd[3794]: xfce4-notifyd.service: Main process exited, code=exited, statu Oct 07 11:29:41 xenial systemd[3794]: xfce4-notifyd.service: Failed with result 'exit-code'. Oct 07 11:29:41 xenial systemd[3794]: Failed to start XFCE notifications service. simon@xenial:~$ exit If I manually edit /usr/lib/systemd/user/xfce4-notifyd.service so that it adds "--display :1" to the command line, then xfce4-notifyd starts up correctly. (But obviously this is a horrible bodge that I only did temporarily for diagnostic purposes :-) So I conjecture that the X display parameter is somehow not finding its way to xfce4-notifyd during startup, and that in the normal case nobody notices because xfce4-notifyd defaults to trying to connect to :0. System details: this can be reproduced on a clean, freshly installed xubuntu 18.04 system (in a test VM, installed on 2020-10-07). The only configuration I performed was to edit my ~/.vnc/xstartup so that it runs xfce4-session (as shown in the transcript above). simon@xenial:~$ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 simon@xenial:~$ apt-cache policy xfce4-notifyd xfce4-notifyd: Installed: 0.4.2-0ubuntu2 Candidate: 0.4.2-0ubuntu2 Version table: *** 0.4.2-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: xfce4-notifyd (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/1898858 Title: xfce4-notifyd fails to start on displays other than :0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1898858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
