[02:13] My screen froze again. I can't really tell whats going on from the logs, though i do see this like a Million times: [02:13] Mar 5 00:01:29 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000129.828661:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 [02:13] Mar 5 00:01:32 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000132.568246:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 [02:13] Mar 5 00:01:34 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000134.119259:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 [02:13] Mar 5 00:01:36 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000136.567160:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 (re @IrcsomeBot: It's the stdout from kwin_x11 I believe.) [02:13] My screen froze again. I can't really tell whats going on from the logs, though i do see this like a Million times: [02:13] Mar 5 00:01:29 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000129.828661:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 === Lord_of_Life_ is now known as Lord_of_Life === tom is now known as Guest1573 [04:34] just reboot to solve gor temporary (re @zparihar: My screen froze again. I can't really tell whats going on from the logs, though i do see this like a Million times: [04:34] Mar 5 00:01:29 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000129.828661:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 [04:34] Mar 5 00:01:32 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000132.568246:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 [04:34] Mar 5 00:01:34 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000134.119259:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202 [04:34] Mar 5 00:01:36 zubin-HP-Z420-Workstation plasmashell[2114916]: [2114916:2114929:0305/000136.567160:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202) [04:34] I pretty much have to [04:35] i just upgraded from 20.04, and in 20.04 I wouldn't need to reboot my system for up to 60 days [04:35] can u share screenshot? i means capture from phone [04:35] basically when I decided to install the kernel update [04:35] I've already rebooted (re @milesdredd: can u share screenshot? i means capture from phone) [04:36] again u have problem? [04:36] actualy what i did was "ctrl + alt + f2" then I restarted 'sddm' [04:36] yes I have the problem every 2 days.... (re @milesdredd: again u have problem?) [04:37] i don't know what problem is this [04:53] Application Launcher will not open files [04:53] If I search and press enter on a file in the application launcher, nothing happens anymore. If I search up a program, it will run. But no file (pdf, txt, document) will open in a relevant program as it used it. Same goes for KRunner. They do let me open the folder with the file, but it's pretty annoying. [04:53] How to troubleshoot it? === aaa is now known as Guest7679 [06:40] guys i have finally managed to enable hibernation in my laptop and i am able to start it by using command line, but i wonder if there's a way to create or enable an hibernation button in the KDE interface or maybe a plugin? === terry is now known as Snoop === Snoop is now known as Terry === Terry is now known as Snoop [07:25] whats the command? (re @Arang: guys i have finally managed to enable hibernation in my laptop and i am able to start it by using command line, but i wonder if there's a way to create or enable an hibernation button in the KDE interface or maybe a plugin?) [07:26] and if u know the command , create a shortcut key , [07:29] how to change it's theme ??? : https://irc-attachments.kde.org/a596ac41/file_63928.jpg [07:32] make sure that these are not uncheck : https://irc-attachments.kde.org/5b123047/file_63929.jpg [07:35] sudo systemctl hibernate (re @milesdredd: whats the command?) [07:35] it will require sudo so i cant just create a script [07:37] They're checked, results appear when searched. It's the action that follows the click on the result that isn't there. [07:37] E.g. I search 'bear' and docs with bear come up in results like 'how to bear grief.pdf' [07:37] Clicking on this should open it in my pdf reader but nothing happens. [07:37] I can still open the container folder (re @milesdredd: ) [07:37] Hi everyone, [07:38] https://paste.gnome.org/bdFipzfni [07:41] i want to be able to get that sweet hibernate button in KDE it is supposed to be able to enable it but it isnt, so i wonder if there is something related to policykit or whatever that helps? : https://irc-attachments.kde.org/026aa061/file_63930.jpg [13:10] Hi all [14:01] I think this place is completely waste :/ only problem owners write their problems but nobody answer [14:45] you should post a summary of your problem here not just the link (re @IrcsomeBot: I think this place is completely waste :/ only problem owners write their problems but nobody answer) [14:52] @Arang, they posted the complaint, then left [18:53] hello guys [19:34] Is there reason for my laptop screen does only 60 Hz since I upgraded to 22.04? It used to be able to do 120 Hz before. Grahics card is a NVIDIA GeForce GTX 1650. [19:35] The external monitor conected via HDMI still can do 60, 120 and 144 Hz, though. === mkv is now known as m4v [19:43] skramer: You use optimus? [19:43] Because if so, I know exactly the reason. [19:43] Well, actually, the likely reason. [19:44] "Exactly" is too strong a word here. [19:44] Please ack and I can share the details. [19:56] mmikowski: I use the proprietary driver [19:57] skramer: Yes, but your laptop very likely uses optimus. This means the panel is not actually directly fed by the Nvidia frame buffer. [19:57] Instead, the NV driver feeds the Intel framebuffer, which is then fed to your panel. [19:57] Now your external panel IS directly connected to the Nvidia framebuffer. [19:58] The Nvidia drivers handle multiple refresh rates very well. [19:58] mmikowski: So I should set it GPU into performance mode? [19:59] However, the Intel drivers, which are used to feed the panel, have different restrictions. [19:59] Specifically on refresh rate support. [20:00] I highly recommend you used Intel for power saving, and performance mode for performance. Hybrid mode actually uses more power than either (!) [20:00] Performance drivers will do nothing for your panel, however. [20:00] It will still use the intel framebuffer. [20:01] mmikowski: But even in Perormance laptop screen offers only 40 and 60 Hz. Up to 20.04 it also offered 120 Hz as well. [20:01] In fact, if you visit Nvidia settings, you will see it labeled as a "prime" display and that you have limited capability to change it. [20:01] Right, as above. [20:01] What is limiting it is the Intel driver, because the NV driver writes to the Intel framebuffer. [20:01] So if you see people who buy laptops claiming theirs "has to have a mux", this is why. [20:02] With a mux, you can connect your laptop panel directly to the NV card, and bypass the intel bugs. [20:02] It's set to NVIDIA On--demand, the option to choose Intel is greyed out [20:03] And get better performance (prime is a bottleneck there too). [20:03] So on-demand is not recommended. It can cause significant slowness and issues when connected to an external monitor. [20:04] So performance mode is better (and will usually save power), so I definitely recommend doing that no matter what. [20:05] But it probably won't fix the refresh rate issue. That comes down to Intel framebuffer issues. Now I have NOT seen this issue on a 120 or 144 Hz display, but I *have* seen it on 160 Hz displays. [20:06] So I will give that a try. Still wonder why I can not choose the Saving mode [20:07] The reason is because of how the monitor presents the refresh rate to the system, and how the Intel drivers cannot read "extended" information. [20:08] In worst case, I still might downgradr to the older driver included in 20.04. Just to find out if it makes any difference [20:08] So the refresh issue on Intel framebuffers is a known issue for some systems. Unfortunately, work-arounds are fragile and would be very difficult to package for all systems. [20:09] Gimme a few secs and I can probably find the Intel bug... [20:09] ... from the database ... [20:09] Okay, thank you [20:10] skramer: You gotta ask, though, what are you really giving up? Does 60 Hz really bug you that much? [20:11] Because rolling back Intel drivers be hard. [20:11] NV drivers are much easier, but that won't do the trick - it's on Intel, not NV. [20:12] Yes as they are built into the kernel, right? [20:13] Yes. Here's the Intel bug: https://gitlab.freedesktop.org/drm/intel/-/issues/125 [20:13] -ubottu:#kubuntu- Issue 125 in drm/intel "xrandr does not correctly switch display refresh rates, but pretends it did" [Closed] [20:13] we're tracking that at Kfocus. [20:13] We have one panel that runs at 160 Hz, but because of that bug, it is not available in Prime. [20:14] However, for people who want maximum performance, there is a mux available so the card can drive the panel directly. [20:14] Then 160 Hz is available. Since people usually want the Mux for max performance in that situation, it works out for most use cases. [20:15] However, it looks like in 5.19+, the fix is already in. [20:16] *165 Hz. [20:17] You might also see if you have a mux. If you do, you can switch that out. [20:17] Not sure why Intel is not available, but there it is. [20:17] kk, best of luck to you. Back to work here :P [20:18] Thanks again. [20:29] skramer: You're welcome! [20:30] fwiw, while 5.19 the "fix is in" doesn't mean it's propagated yet; it might never make it to 5.19, or it may already be there (but wasn't, last time I checked). [20:31] Finally, that may not be the bug, but my hunch is it is. If you have a mux switch in the BIOS, you could use that to verify that at least it is limited to the Intel FB. It certainly looks like it is. [20:32] https://gitlab.freedesktop.org/drm/intel/-/issues/5459 [20:32] -ubottu:#kubuntu- Issue 5459 in drm/intel "High refresh rates broken on eDP display with Optimus" [Closed] === backspin is now known as Guest2265 === Guest2265 is now known as backspin === backspin is now known as backspin_ [22:13] hi all === backspin_ is now known as Guest2491 === guiverc2 is now known as guiverc === jcea1 is now known as jcea