[00:33] anyone know how i can change the color of these drop down menus? https://i.imgur.com/YiDJ8Sa.png cant find the place to set it... [01:01] Want software installation managers are most recommended for kubuntu? [01:30] deeno- if you don't like Discover, Muon should still be available in the repository [01:30] Or there's always the option of using apt from a terminal === lethu__ is now known as lethu [01:54] Synaptic should also be in the repository, if you prefer that ("old-school") kind of approach === kubuntu is now known as FlameStrike === usuario2 is now known as NatashaHack [04:49] anyone help me with a grahpics issue. i think its hdmi scaling i have to do in windows i have a radeon r7 370 vid card and im using ashitty 32' tv for a montior in windows i have to use hdmi scaling 5% to get the screen to fit 1920x1080 its just a little to big without it. seems to be the same thing in kubuntu im using mesa drivers for steam [04:49] games but i am currently using 1680x1050 because i cant figure out how to get 1920x1080 to fit for me [04:55] Landeskog: did you try using xrandr? [04:56] !xrandr [04:56] XRandR 1.2 is the new method of running dual screens in !X. Information/HowTo here: http://wiki.debian.org/XStrikeForce/HowToRandR12 [04:56] huh [04:56] oh yeah, new page, but that's the right info I think [04:56] it's been a long time since I had to use that [05:50] valorie: [05:51] thank you xrandr --output HDMI-1 --set underscan on works from console [05:51] is there a way i can make this perm sorry im very new to linux [05:53] hmmm [05:53] it always stayed permanent for me [05:54] but that page should stay [06:01] hmm [06:04] no it didnt stay on [06:04] for a reboot [06:13] hmmm [06:13] well, perhaps someone will come along who knows how to do that, Landeskog [06:14] thanks for your help [06:14] or you can ask in #ubuntu which is a much larger channel [06:14] this is not really a Kubuntu issue [06:19] everything i see on google says to edit /etc/X11/xorg.conf [06:19] but theres nothing there [06:19] oh, just create it [06:20] in the commandline, `mkdir /etc/X11/xorg.conf` [06:20] if you don't have permission to do that, use sudo before that command [06:20] copy /paste between the ` [06:21] control shift v to paste in konsole [06:23] Is there someone here who can help me? I have just installed Kubuntu on a laptop and I cannot get it to boot. [06:24] FlameStrike: did it finish installing? [06:24] Yes [06:24] and now what happens? [06:25] The machine still tells me to select a proper boot device [06:25] does it boot if you leave the USB in the machine? [06:26] Yes, it boot with the USB drive. [06:26] ha [06:26] I had this happen one time [06:26] I hope what worked for you will work for me [06:27] there is a rare bug where the grub file is written to the USB instead of to your hard drive [06:27] basically you have to write a new grub file [06:27] !grub [06:27] GRUB2 is the default Ubuntu boot manager. Lost GRUB after installing Windows? See https://help.ubuntu.com/community/RestoreGrub - For more information and troubleshooting for GRUB2 please refer to https://help.ubuntu.com/community/Grub2 [06:27] And how do I do that? [06:28] FlameStrike: I would ask in #ubuntu if the above links don't tell you enough [06:28] this is an Ubuntu bug, not really Kubuntu [06:28] Thanks, I'll give it a try. [06:28] it's a lot bigger channel [06:28] FlameStrike, try to disable eri in bios [06:28] and this one is sorta dead right now [06:28] diogenes_: what? [06:29] eri? [06:29] uefi* [06:29] this isn't uefi [06:29] since it will boot with the usb in [06:29] I tried that, and then I couldn't even start from USB [06:30] doesn't happen often, and it's an oooold bug [06:30] because usb should be fat32 [06:30] but since it rarely happens, nobody so far has figured out how to stop it happening [06:30] but writing grub isn't that tough [06:30] I just don't remember how [06:31] Well, I'm loading from the USB now, so I'll see what I can do. [06:33] Good morning. [06:33] ooo, lordievader might know [06:35] iveasked in a few channels im in hoping someone whos decent at nix can guide me i dont think its to hard to do i just dont know enough about linux [06:35] FlameStrike, maybe you could try this http://dpaste.com/2R8F786 [06:35] Any help will be appreciated [06:36] valorie: What might I know? [06:37] FlameStrike's problem, which I was hit by once [06:37] after installing, "select a proper boot device" [06:37] in my case, grub got written to my usb drive [06:38] <[Relic]> cd/dvd/usb or bad hd [06:38] Yeah, that happens. [06:38] Does look that way. [06:39] I didn't use that boot-repair ppa, but it looks legit [06:39] dunno for sure [06:39] as I recall, I had to chroot in to write a new grub [06:39] None of the suggested solutions I've found even mentioned that as a possibility, so any help in trying a fix for that would be appreciated [06:39] it was no fun and took a long time [06:41] FlameStrike, valorie: that is probably the best way. Chroot into the install, from there install grub and update the grub config. [06:42] lordievader: did you see this http://dpaste.com/2R8F786 [06:42] FlameStrike: https://help.ubuntu.com/community/LiveCdRecovery#Update_Failure [06:42] Yes, I personally don't like boot-repair. [06:44] boot-repair is well known solution [06:45] For what it's worth, this is a new HD, so there was no update or OS replacement involved, except for the Windows on the defunct drive that preceded this one. I can't imangine why that would make a difference though. [06:45] FlameStrike: It doesn't ;) [06:45] if you find that old bug report, you'll see that it doesn't happen often, but afaik still happens [06:45] That is, it shouldn't. [06:45] heisenbug [06:46] right, in many, many installs it only happened to me once [06:46] Boot-repair has been tried and found lacking. It's telling me there's no efi partition, when there is in fact just such a partition. [06:47] FlameStrike, so you see [06:47] chrooting in works [06:47] uefi is what's causing the trouble [06:47] ? [06:47] lack of grub is the problem [06:48] And getting rid of uefi prevented me from booting from usb or hd, so that make things worse [06:48] boot-repair should have managed to restore grub [06:48] chrooting works [06:48] FlameStrike, is your usb format fat32? [06:49] FlameStrike: Does /sys/firmware/efi exist in the live environment? [06:50] I think so. I've never reformatted a usb drive, so it's whatever is the default format. [06:50] FlameStrike, open gparted [06:50] and see the exact format of usb [06:51] fat16 on the usb [06:51] FlameStrike: Could you check, that is a directory only created when the usb-stick is booted in efi mode. [06:52] Yes, I can find sys/firmware/efi [06:53] I'd advice you to find a working pc or another usb drive, format it with fat32, burn kubuntu, enable uefi in bios and when you boot press f9, f12 or whaever key responsible for choosing boot device, and give it boot from your usb [06:55] Right, so you do have uefi. Then it could be perfectly reasonable grub is 'missing'. [06:55] FlameStrike: https://help.ubuntu.com/community/UEFI [06:56] The machine is currently booting from usb, that's not an issue. If fat32 and not fat16 is the issue, then I'll give it a try in a bit. [06:57] I'm familiar with that page, it suggests I change BIOS settings I can't even find in my BIOS [06:58] Filesystem should not matter. [06:59] I didn't think it should, but I'm not going to completely write off any possible fix, no matter how unlikely, [07:01] If everything else fails, I suppose you could set the boot mode in the bios/uefi to legacy, i.e. bios mode. [07:01] No, because then I can't even boot from the USB, which prevents me from even trying a new install. [07:02] !chroot [07:02] A chroot is used to make programs believe that the directory they are running in is really the root directory. It can be used to stop programs accessing files outside of that directory, or for compiling 32bit applications in a 64bit environment - see https://help.ubuntu.com/community/BasicChroot [07:02] eh [07:04] lordievader, filesystem matters when it has to deal with eufi boot [07:05] diogenes_: How come? [07:06] lordievader, try to boot from ntfs usb in uefi mode [07:06] valorie: Can't say it ain't true ;) [07:06] and you'll see why [07:06] uefi doesn't see any device other than fat32 [07:06] * lordievader still uses bioses exclusively [07:14] Well, the grub fix, or at least the instructions I found for one, did not help [07:17] What instructions were they? [07:18] I don't recall the address, but they involved chroot, grub-install, mount points [07:20] Here's the address, found it again: http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd [07:23] That is what valorie and I had in mind. [07:24] so what part didn't work, FlameStrike? [07:24] I'm still getting the "proper boot device" message [07:25] damn it [07:25] Not quite how I phrased it, but yeah [07:25] anyone know how i can get xrandr --output HDMI-1 --set underscan on to fuckin stay perm i keep havin to enter than to get 1920x1080 to fit then its gone on reboot [07:27] Landeskog, make a script [07:27] i managed to get grub2 resolution right but my login screen and my tty1 and wrong still [07:27] Landeskog: ^, xrandr settings are not permanent. Make a script and let systemd or something run it for you on boot. [07:28] like a bash script? [07:28] sorry im very new to nix [07:28] i used to play around with it when iwas a kid but been a long time [07:29] Landeskog, what is the command you have to run every time? [07:30] xrandr --output HDMI-1 --set underscan on [07:30] now open terminal [07:30] ok [07:31] run: touch ~/Desktop/myscript [07:32] ok just dropped to next line [07:32] run [07:32] echo '#!/bin/bash [07:32] xrandr --output HDMI-1 --set underscan on' >~/Desktop/myscript [07:32] 2 lines ? [07:32] or one [07:32] one [07:33] just [07:33] copy paste [07:33] done [07:33] tell me when u done [07:33] run [07:33] cat ~/Desktop/myscript [07:33] and tell me what you see [07:34] cat ~/Desktop/myscript [07:34] #!/bin/bash xrandr --output HDMI-1 --set underscan on [07:34] now [07:34] run: chmod +x ~/Desktop/myscript [07:35] done [07:35] now look on desktop [07:35] do you see the file? [07:36] i dont see it but i see it in /home/Desktop [07:37] weird [07:37] right click on myscript and open with a text editor [07:37] ok [07:37] i dropped it down into 2 lines [07:38] you should see the exac this: [07:38] #!/bin/bash [07:38] xrandr --output HDMI-1 --set underscan o [07:38] it was all one [07:38] yeah [07:38] its proper now [07:38] without diogenes [07:38] ok now [07:38] in terminal: ~/Desktop/myscript [07:38] and see if it runs [07:40] Well, I think I'll give up for tonight. I'll try again another day. Thanks for trying to help. [07:41] sorry we couldn't help, FlameStrike [07:41] it ran i think [07:41] you might search for that bug report on launchpad and see if there is any help in there [07:41] and report that "it is still happening!" [07:41] * valorie logs out as well [07:41] Landeskog, now open system setting and go to starup applications [07:42] add script? [07:42] Will do. and I'll be checking the format of my usb drives, just in case it helps. [07:42] Landeskog, yes [07:42] add script [07:43] hmm [07:43] flashdel, yes, format in fat 32 and burn iso again and don't forget, you have to switch uefi ON [07:43] it wont let me add to pre kde unless i make it a .sh? [07:43] Landeskog, DO'T USE pre os [07:44] just startup? [07:44] it should let you add /home/&USER/Desktop/myscript [07:44] will that fix the login screen and the tty1 or just after i login itll be correct [07:45] gonna try a quick reboot brb [07:45] wait [07:45] did you add the script? [07:45] or not [07:47] diogenes_: it worked i guess [07:47] its working after i login perfect [07:47] if it's working there, then it will work after reboot also [07:47] but my login screen and tty1 before i login are still incorrect resolution because i need the underscan to be on [07:47] i rebooted already [07:49] Landeskog, is it alright when you rebooted? [07:51] when i start my pc now. it boots to the grub menu because im dual booting windows 10. the grub menu is 1920x1080 resolution perfect because i edited /etc/default/grub but after i click kubuntu and i see the login screen its at 1920x1080 but its to big for my screen if that makes sense if it hit ctrl f1 or whatever it is to get to the cmd [07:51] prompt tty1 it is also in 1920x1080 but to big for the screen [07:51] hope that makes sense [07:51] but once i login your script activates and its good [07:53] so you want it to fixx your resolution in pre os? before you login? [07:54] yeah i was looking to fix it all [07:54] its not really a big deal i guess it just makes it very hard if somthing happens and gui crashes [07:54] i cant see anything in tty1 [07:54] really [07:56] well now you got the corerect script, all you have to do is to read the docmentation how to make it work in pre os [07:56] you can start with reading this: https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/autostart/ [07:56] and good it a bit more [07:57] I mean google it a bit more [08:04] thanks for the help i appreciate it im readin this now [08:07] https://www.irccloud.com/pastebin/jU1q6MBa/ [08:07] diogenes_: think this would work? [08:10] Landeskog, don't know [08:10] bout to try [08:16] Ain't it better to make an Xorg config for this setting? [08:16] That way both the login screen and the normal session benefit from it. [08:16] The tty won't since it doesn't run X ;) === lordievader is now known as Guest5998 === Guest5998 is now known as lordievader === HmpfCBR_ is now known as HmpfCBR === faLUCE is now known as papero01 === ovidiu is now known as ovidiu_ === ovidiu_ is now known as ovidiu [10:58] Hiyas all === Guest36384 is now known as Haudegen === ovidiu is now known as ovidiu__ === ovidiu is now known as dustbit3dsad [12:11] -_- === faLUCE is now known as espero7667 === enzo is now known as Guest31496 === Guest31496 is now known as Mad_John [15:40] Bonjour! [15:43] Hi Mad_John [15:44] Oh sorry is it an english channel ? I'm new and I'm discovering [15:47] that's fine, your English seems good, but you can join #ubuntu-fr if you wish [15:56] Yes I speak english not that bad, thanks you for the french channel haha [15:58] One last question : how do I join a new channel ? [15:59] One last question : how do I join a new channel ? [16:00] It's ok, I found how to do === wayne_ is now known as wain === wain is now known as roadstar === roadstar is now known as wain === fabien_ is now known as tuxx === IdleOne is now known as Guest93332 [19:57] hey everyone, i have a laptop w/nvidia graphics + nvidia binary installed, and i have a problem with unplugging from an external LCD [19:59] so far, here's what i've diagnosed: working on laptop LCD works OK. plugging in an external monitor (HDMI) works OK. unplugging the LCD works fine. restarting without the LCD plugged in goes into X, shows me a login screen, then goes to a black screen instead of loading KDE [19:59] if I plug in the external LCD and restart, everything works okay. [20:00] switching to another console works OK. killing Xorg + sddm + whatever and restarting it brings me to login, but then it does the black screen thing again. [20:01] now, i tried to delete some stuff in my home dirs to fix the problem, and it does fix it [20:02] what did you remove? [20:02] i'm digging through "history" and trying to remember [20:03] i have done it a few times before too, so I narrowed it down a bit, but it's been more of a trial-and-error approach than anything [20:03] i remember it's definitely probably in ~/.kde or ~/.config or ~/.cache [20:03] or maybe ~/.local [20:04] yeah, it may have been ~/.local/share/ [20:05] never ran into such issue [20:06] https://pastebin.com/XTarbx1x [20:06] here's my session from when I last did this [20:07] looks like it may have been anything in ~/.local, ~/.config, and ~/.kde so not very helpful [20:09] did it have such behavior before you installed nvidia driver? [20:10] I don't think I've ever run without the NVIDIA driver, but I've been through several versions and it's always been the same. [20:10] how did you install nvidia driver? [20:11] wget, chmod +x, ./NVIDIAblahblahblah, mokutil --import, shutdown -r now [20:12] idk? the usual method. [20:13] this is not the recommended way [20:13] you should have used driver manager [20:13] here's the thing, it works fine with choosing "gnome" from sddm login screen [20:13] on either config [20:13] it's only Plasma that breaks, and only after login [20:14] then it's plasma 5 another bug, plasma 5 is the buggiest of all the previous versions [20:16] so... check in #plasma? [20:18] yeah I guess [20:21] I am getting a warning when I doing "sudo service network-manager status". Arping could not be found; no ARPs will be sent. === Guest93332 is now known as IdleOne === Zren_ is now known as Zren === usuario2 is now known as NatashaHack === lethu_ is now known as lethu