| iamempty | hey guys | 00:06 |
|---|---|---|
| mparillo | fuze: No, the Kubuntu Backports will never show in the main repository for an old release. Your uptions are (1) Keep your existing release and apply Kubuntu Backports; (2) Upgrade in place to a new release (3) Backup your data, fresh install, restore your data | 00:57 |
| === denza252 is now known as merbo | ||
| === merbo is now known as denza252 | ||
| kubunted | is it a conspiracy? WHy is linux getting worse and worse? | 02:46 |
| [Relic] | cause they aren't microsoft so they can't claim that all those problems are extra features :) | 02:49 |
| kubunted | [Relic]: it's done without claiming | 03:04 |
| [Relic] | this sucks, done with 17.04 I think, finally got another usb to boot and it craps out the same way as the other one did | 03:32 |
| kubunted | 17.04 no good? i was about to try | 03:50 |
| [Relic] | not sure what it is | 04:01 |
| [Relic] | going nuts trying to figure out what the problem is | 04:18 |
| [Relic] | the iso md5checksum shows good but when it boots it says it has bad files, not sure if there is something I should change in grub that might make a difference, I know I have a very up to date nvidia card (1050 ti) so I expected a little bit of a problem, but still can't get it to work yet | 04:19 |
| === jayhunold is now known as jhunold | ||
| lordievader | Good morning | 06:17 |
| juke_ | Hello! I'm new to Kubuntu and Linux and i got some questions. Can anybody help me please? | 09:16 |
| lordievader | !ask | juke_ | 09:18 |
| ubottu | juke_: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience | 09:18 |
| suici | i can | 09:20 |
| === himcesjf_ is now known as himcesjf | ||
| === rumble is now known as grumble | ||
| BluesKaj | Hi folks | 11:02 |
| aiena | o/ BluesKaj | 11:33 |
| BluesKaj | hi aiena | 11:47 |
| EvilRoey | himcesjf: yes thank you | 12:47 |
| EvilRoey | himcesjf: and Dolphin had this functionality available as a plugin | 12:47 |
| lylil | 0.0 | 13:45 |
| === lylil is now known as ly12lil | ||
| === ly12lil is now known as lylil | ||
| lylil | 0.0 | 13:51 |
| === jemand is now known as Jemand | ||
| himcesjf | EvilRoey: Yes, I vaguely remember that | 14:19 |
| EvilRoey | himcesjf: aye, and the kpart in Dolphin shows it with boxes instead of a radial pie chart | 14:20 |
| lylil | 0.0 | 14:23 |
| lylil | 0.0 | 14:25 |
| iamempty | time | 14:28 |
| Myman | iamempty: The time is now Wed Jun 14 17:28:14 EEST 2017 | 14:28 |
| iamempty | damn | 14:28 |
| iamempty | what is this room abotu? | 14:30 |
| === adam__ is now known as NessInOnett | ||
| EvilRoey | himcesjf: http://feinstaub.github.io/blog/kde/2016/01/29/view-disk-usage-via-dolphin.html <-- this makes it a little more usable | 16:15 |
| himcesjf | EvilRoey: There you go | 16:26 |
| EvilRoey | himcesjf: thank you very much :) | 16:30 |
| [Relic] | How do I figure out what is broken in grub or the iso that keeps causing me not to be able to use the 17.04 usb | 16:31 |
| [Relic] | live from usb | 16:31 |
| [Relic] | it also effected 16.04 which I know I tried on this computer before, but again goes to this weird grub menu when I try to boot | 16:32 |
| [Relic] | the only thing that has changed in my computer since the last time I tried 16.04 was the video card, but that doesn't seem like it should trigger no boot and the grub menu instead | 16:33 |
| BluesKaj | [Relic], grub menu or grub rescue? | 16:35 |
| [Relic] | and the 2 versions of 17.04 that I made into usb sticks and actually try start but then kernel panic error out | 16:35 |
| [Relic] | then read like 25 errors even though I downloaded the iso 2x and installed on 2 different usb drives | 16:36 |
| [Relic] | comes up to GNU Gurb version 2.02!beta3-4ubuntu2 Minimal BASHlike editing supported | 16:37 |
| BluesKaj | [Relic], which app did you use to install the images to the usb stick ? | 16:37 |
| [Relic] | dd | 16:37 |
| [Relic] | tried unetbootin that didn't work well | 16:37 |
| BluesKaj | dd can be tricky if you don't have clean partition target, but disk creator works well too | 16:38 |
| [Relic] | I thought maybe the first usb was bad with the 25 errors, but then I made the 2nd one with 2 <4G partitions and it still errors out the same way | 16:39 |
| [Relic] | I am on 14.04 right now | 16:39 |
| BluesKaj | did you check the md5sums of the images? | 16:39 |
| [Relic] | yep | 16:39 |
| [Relic] | start up disk creator doesn't even see the drive for some reason , niether does unetbootin | 16:41 |
| [Relic] | and yet if I open files with dolphin it is all there and fdisk -l will show it too | 16:41 |
| [Relic] | trying to find where the multi core cpu can be turned off to see if that fixes it | 16:42 |
| BluesKaj | formatted the usbs to fat32 | 16:43 |
| BluesKaj | ? | 16:44 |
| [Relic] | yep fat32 LBA mode c, they boot and start loading but crap out after a while says squashfs files are error/bad | 16:44 |
| BluesKaj | never used lba with fat32, unless that's default and i didn't notice | 16:46 |
| [Relic] | that was the one that was booting up so I just used it for the second one | 16:47 |
| BluesKaj | don't think any special block modes are necessary | 16:47 |
| BluesKaj | formatting jsut clear the usb of data , dd doesn't care what the file system is afaik | 16:48 |
| [Relic] | no clue, but that would be the standard win mode since large size HDs came out | 16:48 |
| BluesKaj | then it's probly default unless you chose it as an option or some such | 16:49 |
| [Relic] | programs seem to format things in b fat32 not lba | 16:50 |
| BluesKaj | what was your dd command ? | 16:50 |
| [Relic] | will be back in a few minutes I am going to try adding a few items to the boot to see if that get better results | 16:51 |
| [Relic] | was -> sudo dd bs=4M if=kubuntu-17.04-desktop-amd64.iso of=/dev/sdc1 | 16:51 |
| BluesKaj | try, sudo dd if=kubuntu-17.04-desktop-amd64.iso of=/dev/sdc bs=4M, no need for sdc1 afaik | 16:56 |
| BluesKaj | or add ,sync after bs=4M | 17:00 |
| BluesKaj | amyway, stuff to do for a while bb in a couple hrs | 17:02 |
| [Relic] | that didn't work keeps crapping out on the sqaushfs files and the multiple cpu cores | 17:17 |
| === gustavo is now known as Guest63363 | ||
| BluesKaj | multiple cpu cores, you must be kidding | 17:51 |
| skomorokh | Got a new laptop for the first time in 7 years. Want to install Kubuntu. Installed Windows first because I imagine it'd mess up Linux, but I don't see a way to set up an encrypted install from the Kubuntu installer without nuking my existing partitions? | 18:05 |
| skomorokh | Does that option exist someplace or do I still need to do luks+dmcrypt/lvm manually in a terminal off to the side and somehow coax it to using that to install? | 18:06 |
| skomorokh | I vaguely remember some text mode debianish installer I could boot into aeons ago when I last did this but seemingly that is no longer an option either? | 18:06 |
| skomorokh | Anyone happen to know of a good guide to the most convenient way to accomplish this on 17.04? | 18:07 |
| BluesKaj | skomorokh, did you try using manual partitioning instead of guided or auto | 18:07 |
| skomorokh | BluesKaj: Yup. But it only has options for setting things as boot, root, swap, etc. Not for setting it to encypted lvm. | 18:14 |
| skomorokh | Found this article that for one person, on Ubuntu, last year, it wasn't possible and had to be done manually: https://www.summet.com/blog/2016/11/26/installing-an-encrypted-partition-with-lvm-dual-boot-on-ubuntu-16-04/ | 18:15 |
| skomorokh | So starts to seem likely that it's still the case, this year, for Kubuntu. | 18:15 |
| BluesKaj | skomorokh, afraid that may be the case | 18:18 |
| skomorokh | Hm. Even without any tooling it would have been useful if the installer had a quick note about that near where it has the manual set up option "NB. encrypted lvm while retaining the whole disk is only possible if you arrange that yourself in the terminal" | 18:20 |
| [Relic] | BluesKaj, since I can't log it it craps out on CPU 2 or 4 every time with an IRQ error message and a kernel panic stop | 18:28 |
| [Relic] | Originally I thought it was something about the MB but since I know I put 16.04 and upgraded to 16.10 on this computer to try it and that 16.04 usb disk I just made doesn't boot but goes into the GNU Grub version... message I am not sure what to look at anymore | 18:30 |
| === EvilRoey is now known as cutebutRoey | ||
| BluesKaj | [Relic], do you have 16.10 ? | 18:37 |
| === cutebutRoey is now known as EvilRoey | ||
| BluesKaj | or are you saying the upgrade to 16.10 won't boot after installing via do-release-upgrade | 18:39 |
| [Relic] | don't have 16.10 | 18:50 |
| BluesKaj | [Relic], do you have secure and qick/fast boot enabled in the uefi/bios? | 18:52 |
| BluesKaj | quick/fast | 18:52 |
| [Relic] | not sure I even have that option | 18:54 |
| [Relic] | 16.04.1 | 18:56 |
| [Relic] | 5 copies of that and one 16.04 | 18:56 |
| [Relic] | I am begining to beleive it is a major "new vid card" problem | 19:35 |
| [Relic] | not sure how to get the grub to force whatever mode the bois/cmos/boot is using for the system that seems to work onto it till it gets loaded | 19:36 |
| skomorokh | is there a shortcut to doing all the proc sys etc. bind mounts you need before chrooting when wanting to regenerate grub / initramfs on a system from a livecd? | 19:46 |
| weboh | I am having trouble using Tor. Is this intentional? | 20:50 |
| IrcsomeBot | <acheronuk> @weboh, doubt it. I've never had a problem | 21:18 |
| === X704 is now known as tiwake | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!