 Hello everyone I'm using Kubuntu 22.04 using Wayland
 And whenever I close my laptop and open it again then I see this weird thing as shown in the video
 The only option left to me at that time is to shut down the system and restart it again
 What should I do in order to get through this problem.
 Please suggest some solutions
[05:05] <DDR> Oh gosh, I haven't got sleep sorted out myself here, some issue with the graphics card not turning back on.
[05:06] <DDR> You _could_ try seeing if 'hibernate' vs 'sleep' works, or disabling sleep when you close the lid. 😬
[05:06] <DDR> But ideally it would just work.
 The graphics card is
 Operating System: Kubuntu 22.04
 KDE Plasma Version: 5.24.7
 KDE Frameworks Version: 5.92.0
 Qt Version: 5.15.3
 Kernel Version: 5.15.0-73-generic (64-bit)
 Or can you switch back to X11 otherwise?
 Yeah I was using that earlier but I am also using waydroid which only runs on Wayland (re @n_holo: Or can you switch back to X11 otherwise?)
 So I wanted to use Wayland
 But getting this issue
 Should a change of Desktop Environment help..?
 Doesn't matter, it's something with graphics server sorry and\or drivers
 Doesn't matter, it's something with graphics server support and\or drivers
 https://irc-attachments.kde.org/354ba0ad/file_66657.jpg
 journalctl -xe
 I ran this command (re @a_k_s_27: journalctl -xe)
 Any idea on what vendor.hwcomposer-2-1 is
 Can anyone tell me a way to report a bug for Kubuntu
[09:43] <mparillo> !bugs
[09:45] <mparillo> Hmm. Is that link 404 for you?
[13:55] <m_tadeu> hi....since amarok seems out, what is recommended for media player and media manager?
[14:28] <mybalzitch> mparillo: is for me
[14:28] <mybalzitch> I wonder if thats a bug
[15:23] <rms> My Kubuntu 22.04 LTS simply froze, could not click anything although my mouse was moving. I believe Plasma simply crashed. How can I resume my work without rebooting next time Plasma crashes?
[15:23] <rms> Was expecting something more stable when I switched from Ubuntu to Kubuntu :(
[15:24] <rms> Going into ctrl + alt + f2 and try to restart Plasma did not work so I had to reboot which is not good when you have many working processes
[15:25] <rms> I have RX6700XT and Ryzen 7 7700X
[17:49] <skramer_> Anybody else experiencing issues with Kup backup? Backup does never start on Jammy while it used to work without problems on 20.04. Any idea how to solve?
[18:23] <joseeduardo> Hey you
[18:23] <joseeduardo> Good afternon
[18:25] <joseeduardo> I need to know if I can remove a driver, specefically radeon, amdgpu if the system doesn't using it.
[18:26] <tomreyn> joseeduardo: those are in the kernel. you could remove the 2d Xorg driver, but first of all i'd say know why you "need to" do this. you probably don't 'need to'.
[18:27] <tomreyn> what's the issue you're trying to solve?
[18:29] <joseeduardo> The upgrade to 23.04 fail with dkms building
[18:30] <joseeduardo> Then just the older kernel working for now
[18:30] <joseeduardo> 5.19
[18:44] <tomreyn> joseeduardo: and the error message was?
[18:45] <tomreyn> maybe you 'just' need more space in /boot ?
[18:46] <tomreyn> you can omit some drivers off initrd, and blacklist drivers generally, too (though the latter would not save space, if space is your issue).
[18:57] <joseeduardo> Guessing one have to recompile the kernel with no radeon amdgpu to reinstall, since the system is running on 5.19 and make such change means nothing in the target 6.2
[19:00] <tomreyn> i don't understand why you'd want a kernel without those modules
[19:04] <joseeduardo> Grub is trying to use the shipped kernel that the installation can't build. Stuck in the boot process and just turning power hard to achieve the boot menu in the next booting process that I guess is possible due bios settings boot sequence...
[19:06] <tomreyn> the real question is: why did the extra kernel module fail to build? and would solving this fix the kernel image?
[19:07] <tomreyn> you can boot into older kernels by selecting them from grub's "Advanced" menu. you can bring up grub during boot by pressing escape (uefi boot) or holding down shift (bios boot)
[19:14] <tomreyn> joseeduardo: to explain: dkms only runs when third party modules (drivers which are not already in the kernel) need to be built. and if it fails to run, then you should inspect what it tried to build and how that failed to build, and fix that.
[19:14] <tomreyn> it won't be related to the in-kernel drivers you mentioned
[19:32] <joseeduardo> As I tried mention dkms doesn't do the work to radeon driver. I'll run apt again, it ever output the error.
[19:33] <joseeduardo> make -j4 KERNELRELEASE=6.2.0-20-generic -C /lib/modules/6.2.0-20-generic/build M=/var/lib/dkms/radeon-si/1a/buil
[19:33] <joseeduardo> d...(bad exit status: 2)
[19:34] <joseeduardo> make -j4 KERNELRELEASE=6.2.0-20-generic -C /lib/modules/6.2.0-20-generic/build M=/var/lib/dkms/radeon-si/1a/buil
[19:34] <joseeduardo> d...(bad exit status: 2)
[19:35] <tomreyn> why are you building this driver on your own?
[19:36] <tomreyn> the radeon driver is already in the kernel.
[19:37] <joseeduardo> warning: the compiler differs from the one used to build the kernel
[19:37] <joseeduardo>   The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0
[19:37] <joseeduardo>   You are using:           gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0
[19:37] <joseeduardo> That's from the make.log
[19:39] <tomreyn> see above
[19:41] <joseeduardo> The compiling process is error prone to a compiler name
[19:43] <joseeduardo> Well thanks for all. Maybe the next version fix all that. Anyway 5.19 I'll try to set grub to directly boot 5.19 kernel.
[19:45] <tomreyn> you probably just need to dkms remove radeon-si
[19:46] <tomreyn> sudo dkms remove radeon-si/1a
[20:06] <joseeduardo> It is shipped in 6.2
[20:06] <joseeduardo> Shipped in 23.04
[20:37] <tomreyn> joseeduardo: i don't think so, there is no package which provides the path of /var/lib/dkms/radeon-si
[20:37] <tomreyn> i believe you installed this on your own.
[20:37] <tomreyn> https://packages.ubuntu.com/search?suite=lunar&arch=any&mode=exactfilename&searchon=contents&keywords=%2Fvar%2Flib%2Fdkms%2Fradeon-si
[20:45] <joseeduardo> I'm figuring out how can one do this mess. The installer tricked me in some yes/no choose option for sure.
[20:46] <joseeduardo> That's was in the upgrading Ubuntu version.
[20:48] <tomreyn> which graphics card do you have there?
[20:48] <joseeduardo> Intel
[20:49] <tomreyn> well, if that's the only one then there is no use in keeping the readeon-si dkms module. just uninstall it.
[20:49] <joseeduardo> HD Graphics 620
[20:50] <tomreyn> but i really, really really doubt that kubuntu would have installed this dkms module anyways
[20:50] <tomreyn> i mean, unless oyu asked it to
[20:51] <tomreyn> and provided some means to put it into place there, because no package provides it
[20:52] <joseeduardo> But the kernel isn't installed. Guessing unistall it in the running 5.19 will mirror in the setting for the intended 6.2 one
[20:54] <joseeduardo> I'm running Lunar 23.04 with previous 5.19 from the Kinetic Kudu
[20:56] <joseeduardo> For sure very strange. no issue in the internet too, exactly
[20:58] <joseeduardo> If there's Virtual Machines software installed
[21:06] <joseeduardo> VirtualBox will require them maybe. just a bet. Good night.