[03:09] <IrcsomeBot> <mr_honestyy> Getting this : https://irc-attachments.kde.org/a8fc6c09/file_68938.jpg
[04:28] <IrcsomeBot> <mr_honestyy> I need to move that file to this folder : https://irc-attachments.kde.org/29c5a5a0/file_68939.jpg
[04:34] <IrcsomeBot> <mr_honestyy> Getting this issue  for long time : https://irc-attachments.kde.org/ec937f75/file_68940.jpg
[04:34] <IrcsomeBot> <mr_honestyy> https://irc-attachments.kde.org/df7c047a/file_68941.jpg
[06:50] <enyc> hrrm. I was asking a question before ....
[08:36] <IrcsomeBot> <mr_honestyy> How i can set the Albert hot key globally in kubuntu 23.10
[08:41] <IrcsomeBot> <mr_honestyy> How i can set the Albert hot key globally in kubuntu 23.04
[10:02] <tomreyn> mr_honestyy: what is "the Albert hot key"?
[10:03] <IrcsomeBot> <mr_honestyy> Ctrl + space
[10:03] <tomreyn> when you are sharing "issues", please try to use text as much as possible. just posting an image is often not enough to describe a problem. describe what you did, what you expected to happen, and what happened instead.
[10:03] <IrcsomeBot> <mr_honestyy> Ok
[10:04] <IrcsomeBot> <mr_honestyy> When I reboot or power off my system i get this msg and it take time like more than one minute to automatically turn off or reboot : https://irc-attachments.kde.org/df7c047a/file_68941.jpg
[10:04] <IrcsomeBot> <mr_honestyy> . (re @mr_honestyy: )
[10:05] <IrcsomeBot> <mr_honestyy> When I reboot or power off my system i get this msg and it take time like more than one minute to automatically turn off or reboot how i can solve this problem... : https://irc-attachments.kde.org/df7c047a/file_68941.jpg
[10:06] <tomreyn> which kubuntu version are you running?
[10:08] <IrcsomeBot> <mr_honestyy> When I reboot or power off my system i get this msg and it take time like more than one minute to automatically turn off or reboot how i can solve this problem...Kubuntu version :- 23.04 KDE version:- 5.27.4Processor :- Intel core i5 Graphics platform:- Wayland : https://irc-attachments.kde.org/df7c047a/file_68941.jpg
[10:08] <IrcsomeBot> <mr_honestyy> . (re @mr_honestyy: )
[10:10] <tomreyn> press escape immediately when then messages seen on https://irc-attachments.kde.org/df7c047a/file_68941.jpg is printed on screen, then see if there is some process which is taking a long time to shut down (and ultimatively failing to do so)
[10:10] <tomreyn> once you know what it is that delays the shutdown, you can focus on fixing this issue.
[10:12] <IrcsomeBot> <mr_honestyy> I press escape many time nothing i see (re @IrcsomeBot: <tomreyn> press escape immediately when then messages seen on https://irc-attachments.kde.org/df7c047a/file_68941.jpg is printed on screen, then see if there is some process which is taking a long time to shut down (and ultimatively failing to do so))
[10:13] <tomreyn> ok in this case let's try this:
[10:14] <tomreyn> !bootlog
[10:14] <ubottu> To get a more verbose log of the boot process, remove "quiet" and "splash" from the kernel boot parameters and add "debug systemd.log_level=info". For info on editing kernel boot parameters, see https://wiki.ubuntu.com/Kernel/KernelBootParameters
[10:14] <tomreyn> boot with these kernel parameters, then shut the system down - you should get more output this time.
[10:22] <tomreyn> actually if you just run    systemctl log-level info    before you shutdown, thuis may be sufficient to get more verbose output
[10:22] <tomreyn> mr_honestyy ^
[10:28] <IrcsomeBot> <mr_honestyy> getting this error when i run this command : https://irc-attachments.kde.org/15c2fe9e/file_68945.jpg
[10:35] <tomreyn> you can just run the command with "sudo" prefixed, no need to "sudo -i"
[10:37] <tomreyn> i.e.    sudo systemctl log-level info
=== VlA is now known as V1A
[10:45] <weedmic> in the end, what did the "albert hot key" turn out to be?
[10:47] <IrcsomeBot> <mr_honestyy> not getting anything : https://irc-attachments.kde.org/d44c0d95/image_2023_09_26_16_17_40.png
[10:50] <tomreyn> mr_honestyy: on a linux shell, when there is no output for a command, it usually means the command succeeded
[10:50] <tomreyn> shutdown now, and you should get to see more (may need to hit escape again)
[10:50] <IrcsomeBot> <mr_honestyy> Ok
[10:51] <tomreyn> weedmic: <mr_honestyy> Ctrl + space
[10:51] <tomreyn> apparently it's some application
[10:51] <IrcsomeBot> <mr_honestyy> I get this : https://irc-attachments.kde.org/b0165a75/file_68947.jpg
[10:52] <weedmic> why call it such a name?
[10:52] <tomreyn> mr_honesty: that's after reboot, but did you get to see more during shutdown?
[10:53] <IrcsomeBot> <mr_honestyy> I do know i a new Linux user
[10:53] <weedmic> I mean I have the "host" key - for right ctrl, and a few other weird things like that.
[10:53] <IrcsomeBot> <mr_honestyy> I am asking for this problem (re @mr_honestyy: )
[10:54] <tomreyn> mr_honesty: you can press ctrl-alt-del to leave the grub prompt
[10:54] <IrcsomeBot> <mr_honestyy> Ok yes I do
[10:54] <IrcsomeBot> <mr_honestyy> Then
[10:58] <tomreyn> if you want to, you can repeat the process: boot normally, then in a konsole window, type  sudo systemctl log-level info    then type   sudo systemctl reboot   (or do whatever you did previously to cause the slow shutdown) and press escape immediately to ensure you get full output.
[10:58] <tomreyn> if this still doesn't work then i'm afraid i don't know what's wrong with my recipe.
[10:59] <tomreyn> the idea of getting more output is for you to see and understand what is the thing that is causing the shutdown to take so long
[11:07] <IrcsomeBot> <mr_honestyy> Getting this just : https://irc-attachments.kde.org/35c8f4d5/file_68948.jpg
[11:08] <IrcsomeBot> <mr_honestyy> https://irc-attachments.kde.org/c29aa200/file_68949.jpg
[11:47] <weedmic> but you already know <mr_honestyy> "albert toggle" = Ctrl + space
[12:07] <BluesKaj> Hi all
[17:08] <givko> I have 2 monitors. can anyone tell me how to scale only one monitor on Kubuntu?
[18:21] <gregor3000> hi, 've had nvidia driver issues at upgrade for some time but not as bad as today at my kids PC. so the issue was that PC apparently went off at some point possibly after autoupdate or triggered. anyway while it would boot i could not get the openGL to work. enabling it in settings resulted in non bootable state. and drivers were not fully upgraded. i uninstalled, reinstalled
[18:21] <gregor3000> nothing
[18:21] <gregor3000> went to older kernel worked just fine.
[18:21] <aiena> I have a kubuntu virtual machine setup in virtmanager it is getting network connectivty through a bridge configured in network manager on the host it gets the static dhcp ip from the real router and internet works but KDE shows the network with limited connectivity why does it say that?
[18:21] <gregor3000> reinstalled new kernel, nothing.
[18:22] <gregor3000> went to recovery, did some repair, booted.it was showing drivers installed. but they were not. so i installed them. PC boots. yes!! finally!! but now it takes 1. min to boot.
[18:22] <aiena> gregor3000, live boot also doesnt work?
[18:22] <gregor3000> 1.5 min
[18:23] <gregor3000> it is just strange as i had a simialr issue myself. drivers update in updater then screen goes black
[18:24] <gregor3000> at the time i saw this my quick fix was go to console TTY2, wait a bit, then reboot. but why does it turn off the screen?
[18:24] <gregor3000> this is what puzzles me as it didn't do this before.
[18:26] <gregor3000> so i was wodnering if anyone else saw this? we both have Ryzens  (7 - 2700 and 5-3600) and we both use nvidia GTX 1650 (different manufacturers) and we both have 22.04 LTS
[18:26] <gregor3000> maybe it is time for an upgrade
[18:26] <gregor3000> i mean kernel. to use HWE or something
[18:35] <gregor3000> additiuonal drivers could not install any driver version and at  same time they showed latest drivers install. so i took to console and did a manual install command and reboot. just to see what would happen. sure enough it worked. but now boot is longer +  plymouth is not working correctly. i dont' have the will to try out game so see if drivers are actually working correctyl
=== floown_ is now known as floown