[01:32] prob a dumb question... what on earth is the Desktop folder used for in your Kub home directory? === blueleaf is now known as Guest24570 [01:33] funny thing.. I have icons on my desktop, but nothing in that folder. I assume the icons are listed in .kde somewhere instead. Still tho... I would love to know the purpose of the /home/user/Desktop folder [01:36] going once.... [01:36] going twice.... [01:36] SOLD to the invisible man [01:37] :) LOL [01:45] Valorie, check out my notes in the #kubuntu-offtopic channel.. might help you [01:49] .......Most of my upgrades on Kubuntu have been from version to version.. This one is from 13.04 to 14.10. Apparently you have to baby step it. Do upgrades, restart, do dist upgrade, reboot, do patches... then wash rinse repeat. Is there no way to get directly to 14.10 from 13.04 [02:28] this was just a regular update in 14.10+plasma 5 that left KDE unbootable [02:28] and instead of waiting and having my son help me rsync my old backup, I tried myself, couldn't do it, gave up [02:28] my bad [02:38] did it leave KDE unbootable OR did plasmashell crap out and left you with no X desktop [02:38] I gave up on Plasma5, and went back to plasma4 [02:40] I may get back around to installing next PPA and plasma5 again, but I am going to wait till I get my vbox from 13.04 up to 14.10 plasma4 Kubuntu and snapshot it first with a detailed note of what it is before I attempt plasma5 again... JUST IN CASE lol [02:41] i kid you not... in that 2 week stretch here recently, I musta installed Plasma5 Full install with 14.10 fresh at least 15 times. [02:41] i thought I was just getting a bad install, or corrupt sectors on HD Platter or some weird crap like that. Then I realized.. This many times can't be a fluke [02:42] 16 pots of coffee later.... LOL [02:44] You would have laughed your butt off at me if you was here. I think I sprouted at least a dozen new grey hairs [02:45] its quiet quiet in here right now. :P [03:00] sorry, was afk for a few [03:00] it was unbootable, but I still had the console [03:01] vivid is great so far [03:01] I might advocate pulling the next PPA if nobody is testing it with good results [03:07] how many others besides me and you are knowingly having problems? [03:08] did you and your son reinstall Plasma5 on your new install? [03:13] also, its ok on the afk thing. I am back and fourth multitasking as well [03:39] VolUTFan: I'm on vivid, which is plasma 5 by default [03:39] so far, so good === kubuntu is now known as Guest32132 [04:33] haven't looked at the codename of 15.x yet [04:37] My son leaned back and his head hit the power strip switch and killed my modem [04:37] good thing its on a different power strip than my box [04:39] #apt-get update && apt-get dist-upgrade should bring me from 13.10 to 14.04 right [04:48] im downloading 15.04 beta1 vivid right now [04:48] ill get around to installing that tommorow or the next [04:48] so what should we do, install debugging and report all bugs back to dev? [05:01] Hi, can I ask questions regarding the 15.04 beta here, or is there a separate channel for the new versions? [05:27] wonko_: better in #ubuntu+1 [05:27] VolUTFan: you might want to join the devel chan, and ask about filing particular bugs [05:27] some should go upstream (to KDE) [05:28] also good to join #plasma [05:28] no, dist-upgrade only upgrades your applications [05:29] `do-release-upgrade` does a release upgrade [05:29] but you do want to do `apt-get update && apt-get dist-upgrade` first [05:29] always [05:30] although you will need sudo in front in each of those [05:58] Thanks! [06:23] Good morning, [07:30] <__jack> Hi, I want to install Kubuntu 15.04 on my Mac but couldn't find an amd64+mac iso. I wasn't find one for 14.04 or 14.10 either. [07:30] jack, we don't have a maintainer for that [07:30] so we can't offer it any more [07:31] no testers either [07:31] there is a 12.04, which you can do an LTS to LTS upgrade on [07:31] <__jack> Oh that sucks :/ Thanks valorie [07:32] if the LTS to LTS upgrade works, then you could test the upgrade to 14.10 as well === Malsasa_ is now known as Malsasa === Malsasa is now known as Guest26491 === Malsasa_ is now known as Malsasa === alien_ is now known as Guest52884 === Fritigern is now known as Fritigern_AFK [14:34] Hiyas all === julien is now known as Guest86031 [15:15] I'm using Kubuntu 14.10, fresh install, and it doesn't recognize my TV's 1920x1080 resolution. I tried setting it with xrandr, which "worked", but then the display on the TV is trimmed by about 4" per side. It has the 1920x1080 resolution, but squished/pinched by the sides. [15:26] draikx, which gpu and what type of connection? [15:28] I'm sorry. That would have been helpful, wouldn't it :P [15:30] GPU is onboard Intel graphics (trying to find the exact model), and I've got the DVI-VGA adapter on it (using KVM switch) [15:31] Intel HD Graphics 4000, 350 MHz - 1.1 GHz [15:31] draikx: Could you pastebin the output of xrandr. And does the kvm switch support those resolutions? [15:32] draikx, yes probly the i915 driver , it's their basic driver for mosy onboard gpus [15:32] most [15:32] If it helps any, lspci output for video ====> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) [15:33] lordievader, sure thing. And yes, it supports my other Kubuntu desktops at 1920x1080. [15:33] draikx it sounds like you need to tell the tv not to overscan. on my tv the setting is called 'full pixel' this will prevent the 4" from being cut off [15:33] draikx, a DVI-HDMI adapter would probly give you the correct resolution if the tv is so equipped [15:34] that's what I'm using on this tv [15:36] lordievader, http://paste.ubuntu.com/10502790/ [15:37] BluesKaj, I have xserver-xorg-video-intel installed. I also did "sudo apt-get install --reinstall xserver-xorg-video-intel" just now, but nothing. [15:37] draikx: Is the TV VGA1? [15:37] rberg_, I'll look through my TV's manual for that setting. [15:37] lordievader, yes. [15:38] draikx: So it is running now on full HD? [15:38] draikx, but DVI to VGA ? that's cutting the resolution [15:38] lordievader, I'd have to reboot for the graphics to take effect, wouldn't I? [15:38] draikx: What do you mean? [15:39] I am on 1920x1080 right now, but with the pinch from when I set the resolution values in myself. [15:40] BluesKaj, not sure how it would cut the resolution, if I have 1920x1080 support on my other VGA computers. [15:40] draikx: Did you need to add a resolution mode? [15:40] lordievader, yes. It wasn't in the list. [15:40] lordievader, highest was 1024x768 [15:40] draikx actually with the DVI-VGA adapter you man need to adjust overscan on the computer.. try that if you cant tell the tv to stop overscanning [15:41] draikx: Ah. Now that is interesting. [15:41] lordievader, right? That's what I don't quite get about it. [15:42] draikx: Hold on, going to test some stuff. [15:42] lordievader, sure thing. [15:44] rberg_, nothing in the manual about overscan. [15:44] draikx, it may expand the proper aspect rastio , but the reolution won't be 1920x1080 on some tvs, one has be sure the VGA input is capable of it [15:45] BluesKaj, it is capable, as it works on that resolution on the other desktops I've got connected on the same KVM switch. [15:46] draikx,just curious, do they use the same gpu ? [15:46] rberg_, as for the VGA option, I have 16:9 and 4:3. It's displaying my 16:9 in a 4:3 ratio. [15:46] BluesKaj, no. [15:47] draikx: I'm trying to find a good way of reading the edid info of the monitor. [15:52] draikx: Ah, is 'read-edid' installed? [15:53] Let me see [15:53] lordievader, no, it is not. Shall I install it now? [15:53] yes, please [15:53] done [15:54] draikx: Ok, open a terminal and point it to /sys. [15:54] Then run "cd $(find . -name edid|grep VGA|sed 's,edid,,g')" [15:55] And pastebin the output of 'parse-edid < edid' [15:56] I am assuming here that find takes the right VGA port... [15:56] Running the "cd $(find . -name edid|grep VGA|sed 's,edid,,g')" command put me in '''/sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1'''. [15:57] Running 'parse-edid < edid' only gave me this output ===> Partial Read... Try again [15:57] draikx: Please give the directory listing of the current dir, and the one above. [15:58] pastebin for you, sec [15:58] Although it could explain why it goes for 1024x768. [15:58] lordievader, http://paste.ubuntu.com/10503007/ [15:59] Hmm, never mind about the other. [16:00] Does 'cat edid' crash your terminal? (you get strange binary output, use 'reset' to reset your terminal) [16:00] It's a 0-byte file [16:00] -r--r--r-- 1 root root 0 Mar 2 07:55 edid [16:01] draikx: Here too, doesn't matter. [16:02] For smiles and giggles, I "cat edid", and nothing. No output, just back to my prompt. [16:02] draikx: Right, as a mortal user? [16:03] Yup, as a mortal normal user :) [16:04] draikx: Login as root (sudo -s) and run "parse-edid < edid" [16:04] I did that, too. Same results. [16:04] I did it as root first, then my user. [16:05] draikx: Then I think that this is your problem. The preferred resolution is taken from the EDID information supplied by the monitor. Your's doesn't supply any. So X makes a (sane) choice. And since 1024x768 is supported by allmost anything... [16:05] At least that is what I think ;) [16:06] lordievader, sounds reasonable. [16:06] draikx: Write a script that upon login adds the resolution mode and sets it ;) [16:06] lordievader, but I'm still left with the borders. [16:07] or use a DVI to HDMI adapter [16:07] I'm looking at an HDMI KVM switch right now, as that might just be a solution to all of this. [16:08] draikx: As rberg_ said a couple of times, that is likely a setting on the TV. [16:10] Though another issue with that path is that one of my desktops doesn't like the new kernels. It just won't display anything. I'd have to boot it up to see which kernel it boots into that allows a display, but newer kernels just say "Invalid Format". The video card is supported (GeForce GTX 660 Ti), so I don't know what suddenly changed there. [16:10] lordievader, rberg_: I did a scan to try to correct things, but it skews all of my other VGA displays. [16:12] draikx, the new kernel module upgraded my 331 driver to the nvidia-340 on the last kernel upgrade [16:13] on a 8400GS [16:14] BluesKaj, I've not been able to login on the new kernel to troubleshoot any of it, but I should be able to login to the working kernel, and probe a few things. [16:15] It's still on 14.04, IIRC [16:15] I've not upgraded to 14.10 because it won't display on the latest kernels. [16:18] yeah, you could login to a VT/TTY and try an upgrade or some exploratory commands [16:20] IIRC, it won't even display with 14.10 LiveCD :( [16:22] Yeah, I just get the spinning glass cube from LG, and the bottom saying "Invalid Format" [16:23] draikx, i was mistaken about the kernel module driver upgrade to nvidia on 14.10, it's on 15.04 [16:25] 3.11.0-15 is the kernel that it works on. [16:25] Anything after that, the TV just displays "Invalid Format" [16:45] draikx: Video drivers are compiled against a kernel, perhaps you forgot to update the driver? [16:56] lordievader, I update the kernel from the running kernel. And even then, why won't the LiveCD work? === marvin is now known as Guest52818 [17:13] draikx: Hmm, does nouveau support your card? [17:15] lordievader, honestly, I don't know. [17:18] I plugged into my HDMI port, and it works great at 1920x1080 [17:18] So, maybe I should get the HDMI KVM switch [17:22] draikx: It is probably the KVM switch not reporting EDID info. [17:30] nouveau is great for movies etc as long as the gpu doesn't have to jump thru graphical hoops like games etc [17:31] well, some games anyway :) [17:33] Side question: why would I get a "no file or directory" when doing ./File.bin? [17:33] It is executable, but it says that that file isn't there. [17:33] $ ./AdobeAIRInstaller.bin [17:33] bash: ./AdobeAIRInstaller.bin: No such file or directory [17:34] I tab-completed the name, and I see it there with ls, and it is 16MB in size [17:34] if you are on a 64 bit OS that usually means you are missing the 32bit compat libs [17:34] That would make sense. [17:34] I did go from 32-bit to 64-bit. [17:34] Moved my home directory over and the such. [17:35] rberg_, happen to know the package I need? [17:35] no I try not to deal with adobe. [17:37] I only need it for Pandora One (desktop app) [17:37] rberg_: Hehe, nice. [17:38] :) [17:47] sudo dpkg --add-architecture i386 that should get you the 32 bit library files [17:48] hey guys :)))) [17:48] peek a boo [17:50] I guess not, VolUTFan, as the kernel is already multiarch, just install the :i386 and/or sudo ap-tget install -f to get dependencies resolved [17:50] draikx, multiarch i think [17:50] .... What OerHeks said LOL ... lets go with that [17:51] :) [17:52] you will have a hard time, trying to install that adobe-air nnapi plugin. firefox switched to ppapi some decade ago [17:55] seems like everyone is trying to migrate toward google chrome. I am not a fan of GC at all. [17:57] well, chrome's addressbar font is hard coded so it's not easy to read from 11ft away on a tv/monitor, so FF is the browser I have to use, otherwise chrome would be fine for my needs [17:59] I would be OK with switching to 'pianobar', but I'm not hearing audio. [18:00] draikx: Change the default driver in /etc/libao.conf to pulse. [18:01] Unit193, thanks. I'll try that now. [18:02] draikx: I also have 'quiet' on a new line, I know it's a config option for it somehow, but been too long to remember. Might help though. :P [18:02] Unit193, yeah, I have it there, too. I just changed "alsa" to "pulse", and saved. No change. [18:03] I know there's a few things that block it. Are there any errors and/or are the tracks 42 seconds long? [18:04] No, pianobar seems to play the full song. [18:05] And, dev=default was commented out/removed? [18:05] Not even there [18:06] Line 1: default_driver=pulse line 2: quiet [18:07] not pulseaudio? [18:07] That's all I have in there [18:08] BluesKaj: Nope, that's correct. === kjcole_ is now known as ubuntourist [18:08] draikx: Right, should be good, hrm... [18:08] Unit193, ok [18:11] I get audio from everything else, except from pianobar (command line) [18:21] draikx: Sorry, can't think of anything else to fix that now. [18:28] It's all good. [18:28] Unit193, thanks for the assist, though. In the very least, I learned about that config :) [18:29] Heh, sure. It's a great application. Pithos also does Pandora, though. [18:30] BluesKaj, lordievader, rberg_: thanks for helping with my video issues. I just ordered the HDMI KVM switch from Amazon, so it should be here in 2 days. [18:31] Unit193, I just installed it. I'll play with that now. [18:33] draikx, good, I'm sure it'll work for your setup [18:33] Unit193, I can't up/down vote a song? [18:34] BluesKaj, I'm sure it will. Now, to make sure that the desktops are able to handle USB keyboard/mouse input. [18:34] draikx: Should be able to, unless the version is too old in the repo and has had an API change. [18:34] draikx: Good luck with that ;) [18:46] how do I get from 14.04.2 LTS to 14.10 in my VM [18:47] VolUTFan: Set it to regular releases, then : sudo do-release-upgrade [18:47] i even went into software sources and moved the dropdown from LTS to Normal release, and apt-get update and then apt-get dist-upgrade but nothing is showing up [18:47] ahh, let me give that one a shot [18:48] Make sure you upgrade before dist [18:49] i did, there was only 1 package to autoremove. [18:50] draikx: Theoretically it shouldn't matter, if you look at the dist upgrade process (the action version jump, not apt's dist-upgrade). [18:52] Noted [18:52] VolUTFan, also, the config for it is in /etc/update-manager/release-upgrades [18:54] Doesn't mean that it ain't bad practice to make sure your system is fully up to date. I'm just rambling. [18:55] im reading that release-upgrades file. can LTS be upgraded to non-lts? [18:55] Plasma5 is slick! It's a little rough around the edges, but a few tweaks and it runs really nicely :D [18:55] howdy ugly_cat [18:56] One default really didn't like is how krunner searched images, files, all that stuff. It took too long to retrieve the results and I kept opening up images instead of applications [18:56] Hi VolUTFan ! [18:56] ITS A PARTY NOW !!! [18:56] LOL [18:59] im going to try it, I have a snapshot. the worst that can happen is it blow up in my face lol [19:01] VolUTFan: Yes. [19:01] what is the correct development channel server [19:02] valorie said #devel but only 1 person in there [19:02] VolUTFan: For Kubuntu? #kubuntu-devel [19:02] ok, let me try that one [19:27] im naming my new vivid test vbox "Coffee". It is the only thing that keeps "me" running [19:27] LOL [19:31] Not that it matters right now, but does anyone know off the top of their head about getting USB support in Vbox? I haven't researched that part yet [19:32] vbox on kub doesn't seem to offer usb support without some mods from what I hear [19:33] Extension pack, not "mods" [19:34] I have no idea. Is there any extension pack? [19:34] Yes. [19:34] it would be awesome if there was. [19:35] how would I go about getting the e-pack for vbox [19:40] VolUTFan: https://www.virtualbox.org go to downloads. [19:40] i was expecting it to be a lot more difficult than that LOL [19:40] thanks === mkv is now known as m4v === mkv is now known as m4v === mkv is now known as m4v === Roey is now known as EvilRoey === soee_ is now known as soee === mkv is now known as m4v === mkv is now known as m4v [23:02] If I am running a fsck against a partition and I a) have to offset the superblock and b) am getting a short read on dozens of succesive inodes shoud I keep overwriting them? [23:06] sounds like you have some bad superblocks [23:07] if you replace the bad superblock with a backup superblock and you re-run fsck and it no longer shows a bad superblock... then no, however if you replace the superblock with a backup that doesn't work, then you will need to choose another superblock backup location and try again. Does that answer your question? [23:07] each time, you would need to check your superblocks to make sure your replacement fixed the problem [23:08] dealing with superblocks can be somewhat tricky. Only reason I know anything about that, is that I didn't want to replace my crapped up drive to do what I was doing at the time [23:08] VolUTFan: well I did a fsck with an offset superblock (the backup) and I'm getting the short read on the inodes. do I keep trying other backups [23:09] yes [23:09] VolUTFan: Thanks. [23:09] what I learned is that not ALWAYS does the backup superblock fix the problem [23:09] each of the backup superblocks is for different parts of the drive [23:10] so maybe the one you picked didn't exactly match the md5 of the messed up superblock area [23:10] Yes I've had issues like that before [23:10] One other thing... [23:10] Just never had this many short reads in succesion [23:10] if you can approximate the location of the bad sectors on the hard drive, and its in a location close to the beginning of the hard drive sectors. [23:11] partition the hard drive, with and unusable partion at the head of the drive, then your usable partition after that [23:12] that way you are isolating the screwed up portion of your drive, setting it out of your way, and moving on with the part of the drive that is stable [23:12] see what I am saying? [23:12] usually when you have installation problems, the problems are at the head of the drive === mkv is now known as m4v [23:13] you can guess the location, or how close it is to the "front" of the drive, by the numeric value of the sector the superblock shows [23:29] I thnk I'm going to install another hard drive and image this partition to it [23:34] VolUTFan: Should be easier to troubleshoot and get the data then === snamo is now known as snamo_ === snamo_ is now known as snamo__ === snamo__ is now known as snamo === snamo is now known as snamo_ [23:42] well right, thats the only way your going to find out where the bad sectors are [23:45] VolUTFan: wonder if badblocks is reliable enough [23:46] a bad block, prob, a superblock no [23:48] VolUTFan: Good point [23:48] if a bad block is present, the installer will most likely skip that block [23:51] Yeah It's about a terrabyte of data so I'm going to do a dd for now so at least I have snapshot [23:52] VolUTFan: Thanks for the advice [23:53] no problem kdebooth