[00:40] Hello. I'm very new at this, so bear with me, please. I installed Kubuntu onto my laptop (hp beats special edition 15-p030nr). Everything was fine, it looked like it installed cleanly and I was able to do whatever. It said I needed to restart to finish everything up, so I did. When I was filling out various things (username, name of computer, etc.) [00:40] I finished and it took me to a black screen. Now I cant get out. I tried restarting, and I get the startup screen, but then it goes back to a black screen every time and I won't get anything else until I hit the power button again, and then it just gives me the same screen saying Kubuntu as on startup. I don't know how to go around it at all, or i [00:40] f I even can. [00:42] Can you switch to different ttys? Usually Control-Alt-F1 through F8 [00:48] That got me to "(computer name) login:" so that's something. [02:23] I want to run a script to use battery power when plugged in then recharge on AC power at 10%. I've set the udev rules however I can't find the battery's location for echo. [02:25] everything else Google has taught is an alert or notification [02:32] fenjamin: have a look at qdbus --system org.freedesktop.UPower [02:32] Example: qdbus --system org.freedesktop.UPower /org/freedesktop/UPower/devices/battery_BAT0 org.freedesktop.UPower.Device.Percentage [02:35] koffeinfriedhof ok thanks! [02:36] fenjamin: yw. You need dbus-monitor to use it in scripts. e.g.: https://stackoverflow.com/a/5345462 [02:39] problem solved. [07:05] Good morning === heinkel_111 is now known as heinkel_flying === heinkel_flying is now known as heinkel_111 === madagu is now known as MadAGu === heinkel_111 is now known as heinkel_flying === kubuntu is now known as Guest87933 === heinkel_flying is now known as heinkel_111 === kubuntu is now known as Guest40076 [11:06] Howdy folks === root is now known as cohnation === heinkel_111 is now known as heinkel_flying === heinkel_flying is now known as heinkel_111 === heinkel_111 is now known as heinkel_flying === heinkel_flying is now known as heinkel_111 === alexandru is now known as alexandru__ [13:29] hi everyone, is there any way to remove sudo and go the usual Debian way of accessing the superuser in Kubuntu (17.10)? [13:29] (without breaking anything, if possible) [13:32] alexandru__: Nothing supported, on [13:32] no* [13:32] !root [13:32] Do not try to guess the root password, that is impossible. Instead, realise the truth... there is no root password. Then you will see that it is 'sudo' that grants you access and not the root password. Look at https://help.ubuntu.com/community/RootSudo [13:37] I know there isn't any, but I'm interested in having a regular user password, and a root password, without breaking much of Kubuntu. [13:39] Well you got the answer. There is no supported way, which is what this channel is for :) [13:39] If you decide to do it on your own... then you are on your own [13:40] Okay [13:40] thanks for the support :) [13:47] ForceRecon: your question about checking errors only, read the priority section in "man journalctl" [13:48] it could be for instance journalctl -p 0..3 [13:48] reading now.. thanks mate === nope is now known as NoFreeNameAviabl [14:15] ... I had to reformat partitions, because I couldn't install grub manualy, error after error, and after it told me it has suceeded it haven't booted. [14:18] NoFreeNameAviabl, do you have any other linux OSs on your pc? [14:29] g [14:32] I've tried fedora, it couldn't load grub too [14:32] I've tried arch, but it culdn't fetch packages from internet even on different DNS servers. [14:32] So I'm on kubuntu now. [14:32] I need some nice terminal emulators [14:33] ok , do you have BIOS or UEFI ? [14:35] ok so you have kubuntu running ok then ? [14:37] Yes, I went for the partition shrink and automatic installation provided, but manually I did this: Installed Kubuntu Custom, mounted it as /mnt, mounted bootpart(flaged: boot, bios) as /mnt/boot, then I did grub-install, and then I didn't get boot. === heinkel_111 is now known as heinkel_flying === sysadmin is now known as bjo === martin__ is now known as martin__008 === juboxi is now known as jubo2 === root is now known as Guest12438 === nope is now known as InvalidPassword [18:31] Why is application still in there, when I have it on another desktop? === heinkel_flying is now known as heinkel_111 [20:18] alright, new desktop computer build and its randomly restarting (running KDE)... it randomly restarts under windows too [20:18] I'm not really sure how to approach this [20:19] erm, when I say running KDE I mean kubuntu... heh... from a net-install [20:40] tiwake: random restarts under multiple OSes sounds like a hardware issue, you might want to try ##hardware also [20:40] dax: I'm suspecting its the processor because the early AMD processors had... well.. a lot of issues [20:40] the early ryzen processors that is [20:41] before I put my computer together I noted the manufacture date, and its an older one [20:42] could try installing amd64-microcode, but Windows would be doing microcode updates automatically so... [20:43] its almost identical to the server I built a month ago, different motherboard, but same motherboard company [20:43] might also wanna make sure you're not having heat problems [20:43] same ECC RAM, same processor, power supply, battery backup... [20:44] I guess I'm not sure what to look for for hardware issues in the logs [20:45] or if I should enable something [20:45] i don't know how AMD does it, but Intel will straight up power off the computer without warning if it overheats [20:45] without there necessarily being anything in any logs [20:46] I did do stress testing, when I first assembled it, computer ran full steam for a whole day [20:46] temps were stable and stuff [20:47] then it started random restarting [20:47] in windows anyway [20:47] linux it does not restart, just flakes out without an actual kernel panic? [20:54] when issues start happening with kubuntu, I and it dumps a lot of EXT4-fs errors [20:54] can't log in or anything [20:55] EXT4-fs would be hard drive usually. but that shouldn't autoreboot the system. [20:55] could be memory, i guess? [20:55] no, it did not ever reboot [20:56] try swapping out RAM? or would it be my SSD? [20:56] if it's not rebooting, my guess would be your storage device first, RAM if not [20:57] hmm [20:57] but again, ##hardware might know better, and would also know how to test it [20:57] its an M.2 SSD by crucial, it should be "good" [20:57] alright alright [21:46] All right people, I've got something weird to report [21:46] I keep losing one of my mouse buttons [21:47] as in, every few minutes it stops recognizing the click event [21:47] *X* sees the event, but windows do not [21:49] switching virtual consoles with ctrl-alt-F1, ctrl-alt-F7 restores functionality [21:49] this started about a week ago [21:49] Any ideas? [22:10] You know how when you hover over something you get a visual indicator that it's possible to click on it? e.g., it turns light blue or something [22:10] Not even doing that [22:10] so it's going into a mode where it's unreceptive to selection activity, or something === sysadmin is now known as bjo [22:30] cd [22:43] Hello. I have a problem with Meta (Win) key not opening app launcher. I'm using fullscreen app dashboard, Alt+F1 is working, but not Meta. I'm on 17.10 with kubuntu-backports, so Plasma 5.11.3. It stopped working in September I think (I was o 17.04 without kubuntu backports back then). On my other computers with clean 17.10 + kubuntu backports install it does work, so it's something with my setup, but I'm not sure know where should [22:43] I start to figure what's causing the problem. Any ideas?