[00:16] austin6598: might be more inline here: #ubuntu-touch [00:28] Is it just me or are there some items missing in the right click menu in dolphin in 15.10? [01:15] Where does kubuntu 15.04 put the default wallpapers? [01:20] Or where does apt-get install kde-wallpapers plasma-workspace-wallpapers save the images [01:20] laters [01:20] ahoneybun: o/ how was your day [01:30] aha! [01:30] dpkg-query -L kde-wallpapers [01:52] Anyone have a how-to on creating packages to install with plasmapkg2 specifically splash screens? [02:22] so the daily from monday installer crashed before I even started [02:42] This it? https://www.kubuntuforums.net/showthread.php?68163-Be-Wily-and-Enjoy-the-Progress-of-Kubuntu-15-10&p=379554&viewfull=1#post379554 [02:52] is there anyway to disable avahi? ive tried an .override, update-rc avahi-daemon disable, and ENABLED_ON_BOOT=0. I have looked through multiple stack exchanges and searched google. [02:52] veXx: What is starting it? [02:53] veXx: maybe it's started via Dbus? [02:53] TJ-: im not sure, it autostarts and i been digging trying to find out what starts it [02:55] that may be it [04:29] have any of you seen this? (read the comment) https://www.facebook.com/kubuntu.org/posts/821704247942702?comment_id=828267107286416 [04:30] some user reported same in #plasma [05:04] Hi, I tried to upgrade to werewolf but I ran into an error http://pastebin.com/r9Ey5s7U can someone advise how I can fix this problem? [05:08] rritoch: Use do-release-upgrade. Kubuntu-do-release-upgrade is known to be broken. [05:09] The fix is release; probably needs to trickle down to mirrors [05:10] Nice, good to hear. [05:12] http://packages.ubuntu.com/vivid/ubuntu-release-upgrader-core [05:13] fix is in python3-distupgrade [05:19] lordievader: Ok thanks. I found a related bug report https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1488843 [05:19] Launchpad bug 1488843 in ubuntu-release-upgrader (Ubuntu Wily) "SRU: upgrader kde frontend fails to start" [Critical,Fix released] === WalterN is now known as tiwake [05:20] lordievader: For now I'm going to try to go from vivid > vivid-proposed > wily which I believe is what the bug solution suggests. [05:20] lordievader: When that fials I'll try do-release-upgrade (note the extreme confidence, lol) [05:20] That sounds like a bad idea. [05:20] fials=fails [05:20] Simply run the do-release-upgrade -d. [05:21] What is -d ? [05:21] This is my first legitimate upgrade, all of my other updates have been via mods to the sources list. [05:21] It is used to upgrade to a development version. Wily is still a development version. [05:22] Do realize what it means to be running a development version. [05:22] Things may break at any point without warning. [05:22] lordievader: Yes, I'm a developer [05:23] lordievader: This server breaks without warning either way (grumble MSI) [05:23] Still, if you have no requirement for a development release I'd stick to something released. Preferably even an LTS release. [05:24] lordievader: Isn't wily scheduled to be LTS? [05:24] rritoch: No, 16.04 is the next LTS. [05:28] Ok, well that's unfortunate. I really like the KDE 5 features but it wasn't worth all of the headaches that were caused by leaving trusty (LTS). Either way this system is already unstable. Do you have any idea when the next LTS is scheduled for release? [05:29] April 2016 (16.04) ;) [05:31] lordievader: Ok, thanks for the assistance. The only reason I was going to upgrade to wily-unstable is I thought I could pin to it and it was going to eventually be LTS [05:34] lordievader: This machine eats GPU's like candy. It's hosted the distruction of 4 R9 280X and apparently has managed to do some damage to the integrated graphics. [05:34] Wut? How? [05:35] lordievader: GPU 1 & 2 were cooked in the first week, can't blame the server for that, the manufacturer didn't use enough thermal paste. [05:35] lordievader: GPU 3 is now filled with artifacts after 2 hours of playing minecraft, and GPU 4 was broken by an electrical storm. [05:35] So that is under warrenty? [05:36] Hehe, talking about a stroke of bad luck. [05:36] lordievader: I'm still not quite sure whats wrong with the IGD, but the HDMI is really screwing up. [05:36] lordievader: No, it's well past the waranty [05:36] Hmm, how is the cooling on the other components? [05:38] lordievader: I have no cooling problems anymore, I upgraded to http://www.aerocool.us/strikex/images/image_stx_air-11.png [05:38] lordievader: It needs to be cleaned regularly, but other than that there's no way that things going to cook. [05:38] Pff, that is a computer case? What a beast. [05:39] Still it is a good idea to check your temperatures every once in a while. Especially those of harddrives. [05:44] lordievader: Yeah, I upgraded to that case soon after the first two GPU's were cooked [05:47] lordievader: I haven't checked in awhile but that case has a dedicated fan for the hard drives. Other than hard shutdowns (cutting power), I haven't had any data corruption. [05:48] lordievader: Oh, I forgot to mention this server also ate a 1100W power supply. I'm starting to suspect I need to find a new hardware vendor. [05:51] lordievader: Anyhow, after the next LTS is released I hope to switch to NVidia and maybe try out a Xeon PHI, is the next LTS expected to support Xeon PHI co-processors? [05:57] rritoch: I am not talking about data corruption. Harddrives simply cannot take high temperatures. 40 C is bad for a hdd. [05:57] No idea if it will support Xeon PHI processors. [06:06] Well, I checked the hard drive temps. The primary hard drive is a bit hot, 41C, secondary 36C (independent, not raid) [06:06] The cores are all 37C-39C [06:07] Meh, that is okay. I'd see if you can increase cooling on the primary drive though. [06:08] lordievader: I probably just need to move it down. It is in the top slot which the fan barely reaches. [06:08] Easy peasy ;) [06:12] lordievader: I'm somewhat confused by this sensors output though. It says Adapter: ISA adapter Physical id 0: +42C (accept I don't have any ISA connections on this motherboard Z87-GD65). [06:13] Isn't it a sensor on the motherboard itself? [06:13] ISA just means the original motherboard I/O access [06:13] As opposed to hanging off a IIC bus [06:17] I'm not so worried about these temperatures. The GPU's burned up ~ 104C [06:18] That's to be expected :) [06:21] Anyhow, I was able to revert back to vivid instead of vivid-proposed before any of the proposed updates were installed. So thanks for saving me from that headache. [06:22] I've been testing Wily for a few weeks and so far it's been stable; plenty of regression bugs, but platform has behaved [06:24] Well, my only problem with Ubuntu/Vivid was that KDE doesn't utilize the second video card (pre-gpu destruction) [06:25] If I put two monitors on the primary video card (pre-destruction) KDE used them, but if I connected a monitor to the second card the screen was just black. [06:26] I was temporarily able to resolve it by hacking startkde to launch a second instance of kde on the second screen but there were still some quirks [06:26] Like the start menu opening on the wrong screen. [06:27] Ultimatly I spent most of my time in XFCE since that was able to detect and use both cards without issues (until the gpu's died) [06:29] I don't remember having these problems with Trusty/LTS, but that was a long time ago. I may have done the startkde hack on that also but it never opened menu's or windows to the wrong screen. [06:33] I use 6 monitors across 3 GPUs with it [06:34] On KDE? [06:35] of course! Unit is terrible for multi-monitor multi-GPU [06:35] s/Unit/Unity/ [06:35] TJ-: Are you using sddm ? [06:35] That or lightdm [06:37] Can you pastebin your sddm.conf ? I couldn't find documentation to set that up properly which is why I ended up modifying the startkde script [06:37] Probably too late now since my GPU's are cooked, but I'll be replacing them eventually [06:38] It's the default [06:40] Hmm, I guess my problem was with my configuration of X. To get the second video card to be enabled I had to manually configure it as a second screen. They ended up as DISPLAY=0.0 and DISPLAY=0.1, apparently what I did was far from the standard configuration. [06:41] Yes, I have 4 X screens [06:42] TJ-: Are your GPU's AMD/fglrx ? [06:42] No, nvidia [06:43] TJ-: Ahh, that's probably why. I really have no intention of continuing with fglrx, it has been a nightmare. [06:45] I just need to find a mid-range (stable) NVidia card to use. This motherboard has built-in SLI support it's just a case of finding cards this machine can't eat. [06:46] The R9's were overkill, they used too much power and there was really no noticable difference between 1 card, or crossfire, since 1 card was enough to drive anything I run on them. [06:48] arent the 960gtx midrange? [06:48] I dunno what one defines midrange even. I have a 770gtx that is a year or two, it still does me fine in all games etc [07:08] Are the GTX 970 Ti's reliable w/linux? It looks like they push out about 1 teraflop max as far as I can tell which with 2 cards (2 teraflops) is probably more than enough for anything I need to do [07:19] :) [07:21] * rritoch 's third PCI port is waiting patiently for a Xeon Phi processor [07:26] rritoch: it's one of the most commonly used cards for gaming at least [07:27] oh, not Ti, but I doubt it'd be much different to GTX [07:27] just use up-to-date drivers from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa and it should be all good [07:32] Fglrx and 4.x kernels are a lot of fun [07:37] I saw something about a new catalyst released now, but I've shunned ATI/AMD hardware on linux for nearly a decade so... :p [07:38] lordievader: I agree 100%, AMD should really warn their customers that they are only usable by IT professionals. To get it to work on debian I had to make adjustments to the drivers source code, I got so fed up with the driver situation that it is the reason I switched to Ubuntu. At least ubuntu ships with a "functional" fglrx driver, at least as functional as is possible given the driver quality. [07:39] As much as I hate to see the my $1200 investment go up in smoke, at least I'll be rid of the fglrx headache. [07:40] (2x MSI R9 280X Frozer) [07:41] surely you dont have to throw them away, there are things like ebay [07:42] rritoch: did you try the 15.9 driver? [07:42] hateball: I'm not, I just need to find a repair shop, the HDMI port is blown on one, and the GPU is blown on the other, If someone could lift the GPU and put it on the other card, at least one of them would be functional. [07:43] hateball: They're physically damaged [07:43] rritoch: oh :| [07:43] hateball: GPU was killed by minecraft, HDMI port was killed by an electrical storm. [07:47] While I'm here, is there some decent configuration tool to "repair" the intel IGD configuration? https://forum-en.msi.com/index.php?topic=261015.0 [07:48] Today it's suddenly using the proper 1368x768 resolution, but still only detects on screen as "default" and only lists the 1368x768 resolution in display settings. [07:49] With the GPU's burned up I'm using the IGD but even that doesn't work properly. [07:50] no xorg.conf leftovers messing things up? [07:51] rritoch: or any weird settings under ~/.kde/share/apps/kscreen [07:52] hateball: I removed my custom /usr/share/X11/xorg.conf.d/00-serverlayout.conf & {$1}/01-screens.conf I guess I need to look at the rest of this stuff to see if any of it could be a problem. [07:52] Hmm [07:52] Where is the driver blacklist? [07:53] I think I remember blacklisting some drivers a long time ago, that may be my problem. [07:53] rritoch: /etc/modprobe.d/ [07:54] I see snd_intel8x0m blacklisted [07:55] The integrated chip is Xeon E3-1200 so I'm not sure if that is the problem. I suppose it can't hurt to remove that from the blacklist. [07:55] well that's just audio [07:56] probably blacklisted if you used hdmi out for audio on the ati cards or so [07:56] hateball: Well, one of the problems is the HDMI audio [07:57] radeon is blacklisted in favor of fglrx, but that shouldn't be an issue since both R9's are physically removed. [07:59] Idon't think that's the problem as I have snd_intel8x0 installed, apparently the *m is a different, less reliable driver. [08:07] Well, this is new. HDMI screen is stable, but the vga is now in 640x480 [08:09] Damn, I think I know what the problem is. When my wife holds the cable the HDMI is stable. I probably need better grounding, she doesn't know it but she's the ground wire right now, lol [08:12] I still don't have any resolution options. This seems to have a mind of it's own. [08:15] Good morning [08:18] Hi Everyone, I am ona fresh Kubuntu 15 but the browser cannot play Adobe shockwave based pages. Any idea? [08:21] Colos: Which browser are you using? [08:22] For Firefox/NPAPI based, apt-get install flashplugin-installer [08:22] hateball its the latest Firefox, default on Kubuntu 15 after apt-get update 40.x [08:22] for Chromium, pepperflashplugin-nonfree [08:22] 40.0.3. [08:29] on my work PC (intel GPU) I keep getting a really slow system after a while - looks like an issue with plasmashell ? [08:30] the load of my desktop (8gb/4core) is load average 2 - this is with all apps closed, the top process in htop is plasmshell and its using 126% of CPU [08:30] there are about 30 processes in htop that show '/usr/bin/plasmashell --shut-up' [08:31] rebooting fixes this but it will happen again over time [08:31] how to troubleshoot further? [08:32] yossarianuk: ask on #plasma [08:33] ok soee: this only seems to happen on my work pc - my home pc (nvidia) this doesn't occur. [08:34] Kubuntu is full of bugs :( gonna switch distro again. [08:36] Colos: Mozilla blocked all Flash [08:37] Flash needs to die. I admit I've been saying that for the past 15 years, but still... [08:37] Colos: it will only allow Flash player versions not known to be actively exploitable [08:38] We don't even have a recent version. Adobe stopped Flash for Linux [08:38] That's what Mozilla's security chief told Adobe :) [08:38] Still does butfix releases. [08:38] True [08:39] But do you really need Flash? Who knows sites that can't work without? I do know one. Some post service in France. [08:39] anyway, its rather a browser/OS war because countless websites use flash/shockwawe so that chrome can play any page while firefox cannot play [08:39] www.forgeofempire.com [08:39] a game [08:40] Colos: That's because Google maintain their own Flash plugin for Chrome [08:40] yeah, while mozilla does not maintain anything for flash.... [08:40] Even Adobe have abandoned Flash [08:40] Ah, games. Ok. But that's not really 'needing' it. There are other games. [08:41] Colos: the problem is web sites that use Flash, it's a well-proven vector for malware due to being so poorly written. [08:41] google has a good reason why they maintain it. bec they know very well, the veryy foirst priority is the endure a 100% user experince in the competition and all IT factors come after [08:42] you will not drop your fav game just bec some browser is not playing it, you rather switch browser or OS [08:42] endure=ensure [08:43] The 'poorly written' doesn't play a part here. Look at Hacking Team's exploits. Just the fact that Flash is active in your browser makes you vulnerable to drive by attacks. [08:43] I would. Lenovo's malware and rootkit doesn't affect Kubuntu, but would you still trust Lenovo after that? [08:45] alvin: "poorly written" includes security vulnerabilities [08:45] You're talking about Flash itself then. Yes, but so is all Adobe software. [08:46] The fact the Adobe cannot find these vulnerabilities before 0-days appear tells us (rather like with Ms Windows) that the development process and code quality is very poor. [08:50] so I have to remove the ethernet and wifi cards from my younger brothers PC in order to make sure he is safe on the web from hackers. but than he cannot play his fav online game. we have to decide we waqnt server level security on apC or jusgt having fun. I think everything should be an option for the user. [08:58] Depends on your situation. As a sysadmin, I remove Flash everywhere. It saves a lot of work. [09:02] I think the problem turned out to be with the bios. I reduced the amount of shared memory, and increased the amount of dynamic memory to max, and disabled multi-monitor and it now works much better. [09:04] Ok, looks like the multi-monitor was still on, but the other changes are in effect. It still doesn't detect available resolutions but at least it's no longer broken. [09:12] Still getting this xrandr: Failed to get size of gamma for output default [09:14] "lshw -c video" reports the display is unclaimed [09:42] Hello. Do i understand it right that kubuntu-ci doesn't supply language packages? [09:43] or, specifically, l10n packages [09:59] rritoch: The xrandr error is usually thrown when the driver is crappy. [10:00] lordievader: Yeah, it's a driver issue, I'm now breaking /etc/initramfs-tools/modules to see if I can get the device driver to use the device [10:00] lspci lists the device, but the driver isn't using it. [10:00] rritoch: What is the output of 'lspci -k|grep -A3 VGA'? [10:01] rebooting right now, but it's Xeon E3-1200 [10:03] rritoch: That is not what I am after ;) [10:04] 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) [10:04] Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7845 [10:04] 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) [10:04] Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7845 [10:05] That is with the -k flag? [10:05] Also !paste [10:06] !paste [10:06] For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [10:06] lordievader: Yes, that was with -k [10:07] rritoch: Hmm, so the i915 driver ain't loaded? [10:07] /used [10:08] lordievader: Sounds about right, I added them to the initramfs-tools/modules but that didn't make a difference. [10:08] What is the output of 'cat /proc/cmdline'? [10:08] I set it as intel-agp\ndrm\ni915 momdeset=1 [10:09] BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=f4d484a2-9241-4930-acbe-d10069bf89f4 ro nomodeset quiet splash vt.handoff=7 [10:09] rritoch: Remove the nomodeset from your kernel arguments. [10:10] I truly believe the [MSI] in lspci is the reason NOTHING works [10:12] Ok, right now I'm reverting my changes to the initramfs-tools/modules once that's loaded I'll work on getting that nomodeset out of grub [10:12] The reason that the i915 driver doesn't load is because nomodeset is set. [10:14] Rebooting now, w/o the nomodeset [10:16] Well, it did some "extra" flashing on boot. I suppose that was the screen detection [10:16] rritoch: Do you have a shell? [10:17] kde is loading now [10:18] Wow! [10:18] Your da-man :) [10:18] rritoch: Could you pastebin the output of 'lspci -k |grep -A3 VGA' again? [10:18] WHen I go to display configuration it now reports I havea samsung monitor, that's a HUGE step forward [10:19] Kernel driver in use: i915 [10:20] :) [10:20] Now let's see if it plays nice with HDMI [10:20] There you go ;) [10:22] 10 bytes out of ... some number of GB, breaking everything... This is the stuff that drives me crazy sometimes. But thank you for the help I never would have guessed that nomodeset thing was the issue. I believe I needed that for one of my fglrx issues and it just carries forwards. [10:24] If only there was some kind of "expert system" just to intelligently, automatically, configure a/v on linux, it would be MUCH easier. [10:25] 99% of the time I drop to a shell for configuration is due to a/v issues. [10:26] Expert as in manually? [10:26] :P [10:27] Expert as in database that can make "intelligent" decisions, such as excluding configuration combinations that are incompatble. [10:28] If it wasn't for the a/v issues, I think the rest of linux is already user friendly [10:31] Ok, this is odd. xrandr reports HDMI2 connected [10:31] But the device still says no signal [10:40] Ok, I guess I just needed to enable it === meep is now known as meepnix [10:42] Now for the final test, HDMI audio [10:45] I had some issue where I couldnt use intel hdmi audio unless I also used the video out, that was annoying. guess that's not a problem for you tho [10:46] I don't know yet. [10:46] I was able to get HDMI audio with the R9's but this is my first time using intel's IDG [10:46] err, IGD === Vito is now known as Guest25208 === Guest25208 is now known as Vito [12:49] Hey all === fewcha_ is now known as fewcha [12:57] hateball: No, and I think I'm going to need to give up on the audio issue for now. The HDMI audio isn't picked up, isn't listed in alsamixer or multimedia. [12:58] rritoch: even after you sent video over hdmi? [12:58] it was the same for me iirc [12:58] that is, device didnt show (or was it hardware muted hmmm?) until I sent video over hdmi as well [12:58] Yes, both were on hdmi [12:58] weird [12:59] I don't even see any HDMI listed in aplay -l [12:59] someone know why Hopper Disassembler crash whenever i open it when im on kubuntu? [13:16] helloooo [13:17] I may need your help to get out of a 5 day hell [13:17] And it might be easy for you guys [13:17] !ask [13:17] 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 [13:19] Yes yes, I was about to write :D so : After a few problems, I don't have anything left on my HDD. I use a USB to liveboot on Kubuntu, to be able to put a copy of Win7 on USB (or DVD) to install it later. The thing is, the hash just goes wrong everytime I install (through WinUSB) and I have to download the iso again. Any idea ? [13:21] No idea about Windows [13:23] I don't think it's about windows, but about WinUSB having a 256 error code, and thus having failed parts of the iso (dunno if I'm clear, sorry) [13:23] pef6000: I dont know if it could go corrupt from running in a ramdisk [13:23] why not just install kubuntu and then do whatever it is you want from a real install? [13:23] pef6000: Did you md5sum the iso? [13:26] lordievader: I checked the sha1sum before and after the copy through WinUSB, and that's where it fails. hateball: I don't install Kubuntu again because everytime I install Win, I format the HDD, thus I lose Kubuntu. And the error shows up mostly during the install of Win. [13:27] Is the iso correctly downloaded or not? [13:27] I.e. does the sha1sum match. [13:27] yes, same sha-1 as written on the website [13:28] Ok, try Unetbootin then. [13:29] install windows first or make sure the NTFS partition is at the begining of the ther HDD, and the ext4 partition next [13:29] Oh, about Unet :D when it's a linux copy, everything is right, but with the Win copy, it boots back everytime I press Enter (or leave the 10 automatic seconds) [13:30] BluesKaj: What do you mean, install windows first ? Because the problem is, I cannot burn the iso "correctly" on usb or dvd [13:31] You can pre-partition your HDD, and install Kubuntu. However when you install windows it will overwrite the MBR so you'll need to !fixgrub [13:31] windows doesn't recognize linux/ext drives and as hateball says you lose the mbr or uefi /boot [13:33] pef6000, also I've heard installing windoes from a USB can be difficult on newer pcs [13:33] err windows :-) [13:35] There is also the option of just installing Kubuntu and placing Windows where it should be if it has to be used, contained in a VM [13:36] Arf, I'm sorry, but I'm a newbie. BluesKaj: it's a 5 year old pc, but I guess I can understand :D So, am I supposed to reinstall Kubuntu on HDD, and partition it, like 50-50, and use the other half to try installing Win ? What is the !fixgrub ? (I know grub, but, where and how do I do this, I mean) [13:37] I still need Win for stuff like Adobe CS6, etc [13:37] I mean, through a VM, it would be hard, wouldn't it ? [13:38] pef6000, which windows OS was installed on the pc when you bought it? [13:38] It was 7 [13:38] Well no, I installed 7 [13:40] if it was Windows 8 then you don't have a BIOS. It's been replaced by UEFI which uses a different boot system then mbr [13:41] than mbr [13:41] !fixgrub | pef6000 [13:41] pef6000: 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 [13:41] No, 8 wasn't out yet :D [13:42] ok ,then that makes things easier, BIOS is much easier to deal with IMO [13:42] Thank you, I'll check [13:42] pef6000: most VM solutions have gpu passthrough today, shouldnt really have any performance issues I think [13:45] Mmmh, hateball, I suppose it's possible. But still, I'm kind of fixated on Win7, prefering to have multiboot at most. That was my plan at the beginning but I got a few problems with Manjaro, then Kubuntu, that's why I'm trying to get back to Win :p sorry huhu === toscalix__ is now known as toscalix [13:46] BluesKaj: That's good to read. Thus, I suppose I'll install Kubuntu, make a partition, and retry WinUSB ? [13:48] no, prepartition NTFS andf ext gparted with live media, install Windows first, then kubuntu [13:49] with gparted live media that is [13:50] BluesKaj: The issue is that he cant get the windows iso working using the live media, for reasons unknown. So it might work better using an installed Kubuntu not running from ramdisk [13:51] Alright, so I do as BluesKaj said, gparted to create ntfs and ext4, install Kubuntu on ext, and retry through it ? [13:51] ootherwise windows will wipe out the mbr bootloader which kubuntu installs [13:51] Yes, it will wipe MBR. But you can fix GRUB using kubuntu live-media later [13:53] is it normal to have lag durring the switching to workspace grid animation? [13:53] Trec: Depends on how powerful hardware you have I suppose [13:53] mine is powerful [13:54] pef6000,to solve your problem burn the windows iso to a cd and use that instead of usb if possible [13:54] BluesKaj: I already did, I get the same problem :/ [13:56] then your windows iso image must be corrupt [13:56] Trec: heh, well what gpu + driver do you have? I get some stutter on my Intel HD3000 when I expose 4*2 workspaces... but it is smooth on another machine with nvidia gtx770 and proprietary driver [13:56] happily, it's rewritable. Anyway, I just finished partitioning, I'll install Kubuntu now [13:56] Trec: Also, what opengl render have you set for kwin? [13:56] gtx670 and 340 nvidia driver [13:56] hateball, [13:57] hateball, 3.2 opengl [13:57] Trec: hmmmm [13:57] Seems so, but it works for everyone else, that's what bugs me :/ [13:58] Trec: Well then I don't really know. You could try upgrading the driver using the new PPA https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa [14:03] hateball, thanks [14:07] I believe I found my audio problem https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457369 [14:07] Launchpad bug 1457369 in linux (Ubuntu Vivid) "kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel" [Critical,Fix released] [14:07] I haven't confirmed it, but aplay -l doesn't list my HDMI cards [14:07] well, my hdmi [14:08] I booted to kernel 3.13 and the card is listed [14:08] How do I get the corrected kernel from vivid-proposed? [14:08] Do I need to convert my entire system to proposed? [14:08] Ok guys, I'm leaving, I'll be installing Kubuntu on ext. I'll be back later. Thanks for the help ! [14:09] rritoch, still have pulseaudio ? [14:09] I have it installed, but no it doesn't detect the HDMI audio on the latest kernel 3.19-20 (or something like that) [14:10] The audio is detected with kernel 3.13 though [14:10] if fix is released after -18 it should be in -20 shouldnt it [14:10] hmmm [14:10] usually pulse causes the opposite problem , it won't give any output options other than hdmi in some cases [14:11] rritoch: well you can hold all packages but the kernel. you could also just use the mainline kernel ppa to get a recent one [14:11] I'm not sure, I have the same exact issue that was noted in that bug report. The bug report says it's in proposed [14:12] the solution I used was to purge pulseaudi and pulseaudio-utils on my intel-hda audio equipped machines. [14:13] alsa works perfectly fine with the intel chips without pulse [14:13] Well, I have no need for the latest kernel if it doesn't work. I think I'm just going to stick with 3.13 for now as long as the graphics and audio are working. [14:14] I still need to confirm 3.13 is functional but it appears to be. [14:14] rritoch, regressing the kernel works , but it's more drastic then dumping pulse, but to each his own [14:15] than [14:15] Well, this is already a known issue so hopefully it won't exist for long. [14:16] if it's already in proposed it'll trickle down soon enough [14:18] IME audio problems take a backseat to so called "more serious issues" [14:37] Well this has been fun. 3.13 detects the audio but I still have no signal on HDMI [14:38] 3.19 has a signal and no audio, just can't win this one. [14:41] rritoch, open alsamixer in the terminal and make sure automute is disabled [14:42] BluesKaj, automute is not the issue. With the latest kernel the HDMI audio isn't even detected, IE doesn't even show up in alsamixer [14:44] Anyhow, I'm done for the day. THis damn server has now managed to destroy 5 GPU's if you now include the fact that the integrated GPU doesn't even work. [14:44] rritoch, IE? [14:46] IE is latin, apparently for id est "that is"... [14:47] It did have a signal earlier today, but now it has no signal (in bios so the kernel has nothing to do with it) [14:47] ubuntu-server? [14:48] rritoch, well my latin's a bit rusty, you'll have to forgive me on that one [14:53] BluesKaj: That's fine, I use ie all the time, and didn't really know what it stood for, had to look it up when you asked. [14:53] I just knew what it means. [14:55] Anyhow, no signal so it's game over, this server and MSI for that matter, can go perform an un-natural act. [14:56] rritoch, check alsamixer again to enable spdif , no MM , should shoe 00 [14:57] show rather , normally spdif is the didgital feed to the hdmi out [15:00] BluesKaj: It isnt' worth it, I've had this piece of shit for a year and a half and it's only had about 6 months where it was functional. [15:00] It has now eaten a power supply and 5 GPU's [15:02] what has? [15:03] This computer. It ate a 1100W power supply 4 R9 280X, and it's IGD. (MSI GD65 Gaming). [15:04] heh , maybe the PSU is at fault...poor voltage regualation and filtering can cause any number of problems ..and 1100 watts is prettty big, when it misbehaves , goobye hardware [15:07] the mobo seldom causes other hardware to fail...I'll bet it's the PSU [15:07] BluesKaj: That is highly likely. The 2 GPU's went first, then the power supply, about a month ago the third GPU went, and the fourth GPU died a few days ago, and the IGD died today. The VGA port still works though (for now). [15:08] After the power supply died I just let this thing gather dust for awhile because I didn't want to keep feeding it more hardware. [15:09] nope I don't buy that, with that much HW failure then the PSU was failing and causing other HW to die [15:10] Well, it is possible the bad PSU was partially to blame, everything that has broken was exposed to that PSU, but they didn't die immediately after the PSU was replaced. [15:10] If anything the PSU just degraded the hardware. [15:10] yes, exactly [15:12] it was the root of the problem all along ...I had a similar situation a while back [15:14] this PSU wasn't big , but it was spiking the HW , weakening the more susceptible lower voltage circuits [15:17] anyway BBL === dgm816` is now known as dgm816 [15:20] My KDE restart button doesn't work, how should I diagnose? [15:21] zaggynl: I've had that problem intermittently. Did you run updates recently? Some updates restart properly some don't, at least with ubuntu vivid. [15:22] I run updates daily [15:22] so it needs a reboot to fix? heh [15:22] well I guess I can just sudo reboot [15:23] Upgrade: unity-settings-daemon:amd64 (14.04.0+14.04.20140606-0ubuntu3, 14.04.0+14.04.20150825-0ubuntu1 [15:23] is last update [15:23] zaggynl: Well, if you can get to a root shell, (or ssh), `telinit 6` still works for the most part. If it hangs than I just do a hard reset. I suspect my reboot problems were with fglrx because I couldn't even kill -9 the X server in some cases. [15:23] hm, why does it still have unity [15:32] seems to be fine after a reboot, heheh [15:49] hi [15:57] any chanel someone can suggest [15:57] please [15:58] !alis [15:58] alis is a services bot that can help you find channels. Read "/msg alis help list" . For more help or questions relating to alis, please join #freenode. Example usage: /msg alis list #ubuntu* or /msg alis list *http* === ubuntu is now known as Guest12693 === rthomsen6 is now known as rthomsen === kubuntu is now known as Guest39056 [16:31] guys how should I install nvidia drivers from ppa? Should I remove previous nvidia driver? should I turn off x server? === Guest39056 is now known as kubuntu__ [16:32] guys how should I install nvidia drivers from ppa? Should I remove previous nvidia driver? should I turn off x server? [16:32] kubuntu__, which ppa ? [16:33] nvidia drivers [16:33] do you have a url ? [16:33] you add teh ppa then you install the package.. if its the same name and a newer version it will replace what you hve installed [16:35] https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa [16:35] do I disable the open source driver? [16:35] use the driver manager in system settings it will do that for you [16:36] so install driver from ppa then use driver manager to switch [16:36] ?? [16:36] the module in system settings will also install the driver you pick [16:37] no there is no 355 driver the latest is 344 I want 355 [16:37] you need to update your package list (sudo apt update) before you can see stuff on that ppa... [16:38] there is 340 latest driver do you have 355 there? [16:38] no i don;t ahve any nvidia gfx.. [16:38] yes there is no 355 maximum is 340 [16:38] so I want to install from ppa [16:38] did u update your package list before you looked in the system settings module? [16:38] when the new driver installs it should automatically uninstall the existing driver [16:39] how do I know which driver is being used, there's an open source driver too [16:40] what one is checked in the kcm for drivers? [16:40] yes I think what's kcm? [16:40] a module for system settings. [16:41]