[10:05] <BluesKaj> Hiyas all
[10:48] <lordievader> Good afternoon.
[11:29] <murthy> BluesKaj: are you there?
[11:30] <BluesKaj> murthy, yes
[11:32] <murthy> BluesKaj: Is the autospell check work in konversation?
[11:32] <BluesKaj> no
[11:33] <murthy> BluesKaj: This happens in quassell and libreoffice too. I think I know why
[11:34] <BluesKaj> murthy, ok , what's causing it in your estimation?
[11:34] <murthy> Quassel and libreoffice use hunspell for spellcheck in the background. If hunspell does not find the required dictionary for the selected language for spell check by the user then it fails
[11:34] <mparillo_> murthy: BluesKaj: If you think you know why, could you comment on https://bugs.kde.org/show_bug.cgi?id=349151
[11:34] <murthy> mparillo_: I saw that
[11:35] <murthy> mparillo_: I have been try to figure this out for the past week
[11:35] <murthy> First I thought this is only for Indian users
[11:36] <murthy> Can you guys do something for me to see if this gets solved?
[11:38] <murthy> Goto system settings-> regional settings -> "spell check" on the left panel and then tell me what is the default language set there?
[11:40] <murthy> mparillo_: BluesKaj  any of you trying ?
[11:42] <BluesKaj> murthy, mine's set to Canadian English which I chose in Konverstaion, so it probly reset from whatever the default was
[11:43] <murthy> BluesKaj: ok let me check if canadian english dictionary file is installed by default
[11:44] <murthy> BluesKaj: no the canadian english dictionary is not installed by default. Is you install the hunspell-en-ca package autospell check will work
[11:45] <murthy>  If you install the hunspell-en-ca package autospell check will work
[11:45] <BluesKaj> ok murthy, thanks , I'll do that
[11:46] <murthy> BluesKaj: If that solves the problem tell me, I will update this in mparillo_bug report
[11:47] <BluesKaj> not working yet
[11:47] <murthy> BluesKaj: did you restart konversation?
[11:47] <BluesKaj> let me restart
[11:47] <murthy> ok
[11:50] <BluesKaj> Murook, no luck , tried the word comitee ....no indication/underline
[11:51] <BluesKaj> murthy, ^ rather
[11:52] <murthy> BluesKaj: oh, let me check in konversation, I am using quassel right now
[11:54] <mparillo_> murthy: mine is set to American English
[11:54] <mparillo_> Want me to re-start knoversation also?
[11:55] <murthy> BluesKaj: autospell check is working in konversation. Can you try resetting the language in the regional settings and uncheck and recheck the autospell option in konversation?
[11:55] <murthy> mparillo_: no
[11:55] <BluesKaj> suddenly konverstion seems very sluggish
[11:56] <murthy> mparillo_: american english dictionary is installed by default. You could try to reset the default language in the regional settings
[11:56] <murthy> BluesKaj: strange
[11:57] <mparillo_> KDE regional settings in System Settings, not the language in the selction (<-) in konversation? Nothing improved when I switched the konversation to UK English.
[11:59] <BluesKaj> auto spell check doesn't work , but the manual "check spelling" in the context menu dialog does work
[12:00] <murthy> mparillo_: I mean the regional settings in system settings.
[12:00] <murthy> mparillo_: Did you try resetting the language in the spell check default language?
[12:02] <murthy> The funny thing is American IN was set as the default language for me, but after I changed to American english, the American-IN option disappeared
[12:02] <mparillo_> Just now, I changed to UK English and applied. color colour neither is highlighted. Should I re-start konversation? P.S. Like BluesKaj, manual spell-checking does work in konversation.
[12:03] <murthy> mparillo_: ya try restarting
[12:03] <BluesKaj> ok , I'm dual booting so I'm gonna check my other install, bb in a few
[12:03] <murthy> ok
[12:04] <mparillo> color colour: It works. Now color is incorrect.
[12:04] <mparillo> Should I try changing it back?
[12:05] <murthy> mparillo: so autospell check works?
[12:05] <mokush> dolphin is being `kept back` by apt when I'm updating packges? any idea what that's all about?
[12:05] <murthy> mokush: in 15.04?
[12:06] <mparillo> Yes, in UK english, after I changed my system settings > regional settings > Spell-check language, and changed to UK English.
[12:06] <mparillo> I would rather use UK spellings than no spell-check at all.
[12:07] <murthy> mparillo: can you check if hunspell-en-us package is installed for you?
[12:07] <mparillo> https://bugs.kde.org/show_bug.cgi?id=349151
[12:07] <mparillo> Sorry
[12:07] <mparillo> Installed: 20070829-6ubuntu2
[12:08] <mparillo> So, I will try to change my spelling language back to US English and see what happens.
[12:08] <murthy> mparillo: Ok can you switch back to american english and see if it works?
[12:08] <murthy> mparillo: also restart konversation after that
[12:10] <mparillo> That's funny, the original US English is missing from my drop-down
[12:10] <mparillo> Now the closest I see is American English (United States) [GB]
[12:10] <murthy> mparillo: ya, there is the problem for all of us, something is wrong in there
[12:10] <murthy> mparillo: ya, that one is also present in my system
[12:11] <mparillo> It used to say it was being used, but maybe it never was, because it was never really there?
[12:11] <murthy> mparillo: for me american english IN was present. after resetting it disappeared
[12:11] <mparillo> So I will pick American English (United States) [GB]
[12:12] <murthy> try that
[12:12] <BluesKaj> same on konversation  15.04 . of course it's also v1.6
[12:14] <mparillo> color colour: Color is still wrong with American English (United States) [GB]
[12:15] <murthy> mparillo: since GB varient is used doest it mean that the spell check is working?
[12:16] <murthy> mparillo: From my experience "American English (United States) [GB]" mean english uk
[12:17] <mparillo> Ahh, that explains it. It is certainly working. fgkjaf is flagged as is flavor. However flavour is correct. That means (contrary to my expectation) American English (United States) [GB] is not American English.
[12:17] <murthy> ya
[12:18] <mparillo> I can live with it, but I think some can consider it a bug). I will try to update the bugzilla, but I wonder if it is Kubuntu packaging then and not a konversation bug.
[12:18] <murthy> Now the devs have to give an Info of how these list is formed
[12:20] <murthy> mparillo: I have been scratching my head for the same question, is it an upstream or a downstream one
[12:23] <mparillo> It looks as if somebody re-assigned my bug to frameworks-sonnet
[12:23] <murthy> BluesKaj: Did you try resetting the language in regional settings like mparillo did?
[12:23] <BluesKaj> yes, as i said only the manual spellcheck works
[12:25] <murthy> mparillo: It correct the problem is not with konversation
[12:25] <murthy> BluesKaj: Can you try the solution given in the bug report>
[12:26] <murthy> BluesKaj: The fellow is suggestion to install aspell-en
[12:26] <murthy> *suggesting
[12:27] <BluesKaj> aleady installed
[12:27] <murthy> ya for me too
[12:27] <mokush> the spell checking issue is also in kate https://bugs.kde.org/show_bug.cgi?id=343313
[12:28] <murthy> mokush: nice find
[12:30] <murthy> BluesKaj: Did you try american english?
[12:31] <BluesKaj> yes
[12:32] <murthy> both in regional settings and in konversation?
[12:32] <BluesKaj> yes
[12:32] <murthy> ok
[12:35] <mparillo> BluesKaj: Can you try: "American English (United States) [GB]"
[12:37] <BluesKaj> mparillo, I did
[12:37] <murthy> https://en.wikipedia.org/wiki/Sonnet_(software)
[12:38] <murthy> My guess in there is some error in importing kspell's config files by sonnet
[12:39] <murthy> mparillo: Did you upgrade from 14.10 or its a fresh install of 15.04?
[12:42] <BluesKaj> ok , got stuff to do ....bbl
[12:44] <mparillo> Fresh install of Daily Build of Wily (15.10)
[12:44] <murthy> ok
[13:03] <eXistenZe> Hey guys
[13:04] <eXistenZe> Are there any kind of paid linux apps/packages/software etc?
[13:04] <eXistenZe> Besides some paid distros
[13:07] <lordievader> eXistenZe: Yes, look at the Ubuntu software center.
[13:08] <lordievader> The Ubuntu software center offers paid applications, I mean.
[15:29] <foormea> hello. having a slight issue on kubuntu vivid. in my dolphin's "places", home/network/root/trash are shown 3 times. even if i remove them, they'll always reappear. if i add a custom entry, that entry will disappear
[15:29] <foormea> the disappearing/reappearing happens just a few seconds after deleting the double/triple entries
[15:29] <foormea> i'm on dolphin 15.04.0 kde 4.14.7
[15:34] <BluesKaj> foormea, are you removing or hiding , try the latter
[15:35] <foormea> BluesKaj: i could do hiding, yeah. but why is it showing up 3 times in the first place though?
[15:42] <foormea> BluesKaj: uhuh dolphin is crashing when i start hiding entries...
[15:42] <BluesKaj> foormea, which plasma version, 5.2 ?
[15:43] <foormea> BluesKaj: not sure how to check that. i did use the ppa to try the newer thing, but i removed it from apt sources later
[15:46] <BluesKaj> foormea, ok
[15:47] <BluesKaj> and you've updated/upgraded your packages etc
[15:48] <foormea> BluesKaj: i have
[15:48] <foormea> BluesKaj: how do i check which plasma version i use?
[15:54] <BluesKaj> foormea, in your packager manager/muon search plasma-desktop , it should show something like 4.5.3.1 in technical details
[15:54] <BluesKaj> err 4:5.3.1
[16:00] <foormea> 4:5.3.0-0ubuntu1~ubuntu15.04~ppa1
[16:02] <BluesKaj> ok then it's up to date, foormea
[16:02] <BluesKaj> sorry , I have to go
[16:22] <eXistenZe> hey guys
[16:22] <eXistenZe> is it possible to use 9p virtio to share folders with a kvm guest in kubuntu?
[16:23] <eXistenZe> this tut fail at the /usr/bin/qemu-kvm not found http://www.linux-kvm.org/page/9p_virtio
[16:27] <lordievader> eXistenZe: 9p is one way to do that, yes.
[16:28] <lordievader> eXistenZe: It is easier to use the second approach from your link, the virt-manager approach.
[16:30] <eXistenZe> ah f***... I thought those where two steps and not two alternatives
[16:34] <eXistenZe> how do you mount the folder in a windows guest?
[16:35] <lordievader> Does Windows even support 9p?
[16:35] <lordievader> I think you are better of with samba in that case.
[17:04] <eXistenZe> hum... messed up something at samba install
[17:05] <eXistenZe> when I enter nettwork->samba -> workgroup it now asks for a password
[17:05] <eXistenZe> which I did not set up
[17:11] <lordievader> I have never had any success setting up samba that way.
[17:11] <lordievader> Just use the good old cli way ;)
[17:11] <eXistenZe> I did not set up anything yet
[17:12] <eXistenZe> just installed samba with apt-get
[17:12] <eXistenZe> but I did use the samba network to access my other pcs with shares
[17:14] <lordievader> eXistenZe: https://help.ubuntu.com/community/Samba/SambaServerGuide
[17:22] <eXistenZe> If setting up samba server conflicts with my LAN workgroup, I will have to find another method
[17:22] <victor__> hi guys, i installed a  plasma theme via systemsettings5 and now i want to uninstall it but i don't find the file, where is it stored?
[17:23] <victor__>  hi guys, i installed a  plasma theme via systemsettings5 and now i want to uninstall it but i don't find the file, where is it stored? (Kubuntu here)
[17:27] <lordievader> eXistenZe: It shouldn't.
[17:33] <eXistenZe> can't figure the password
[17:33] <eXistenZe> it's not the user password
[17:33] <eXistenZe> it's not the password set in the KDE configuration GUI
[17:34] <eXistenZe> it's not the password set in smbpasswd
[17:35] <genii> If you used smbpasswd to add a user, use it also with -e to enable that user
[17:36] <eXistenZe> done that genii
[17:36] <eXistenZe> does it need a full system restart?
[17:36] <genii> Not usually
[17:36] <lordievader> eXistenZe: What password are you talking about?
[17:37] <eXistenZe> in dolphin -> network -> samba shares -> workgroup
[17:37] <eXistenZe> it now asks a username and password
[17:38] <eXistenZe> I assume it's the samba server
[17:38] <lordievader> Ah, yeah. Never did anything with that. Not needed.
[17:38] <eXistenZe> It only started to ask a password after I installed samba server. Before it showed smb shares from other pcs
[17:40] <eXistenZe> plus kvm virt manager is still not accessing 10.0.2.2
[17:42] <lordievader> eXistenZe: Is smbd running? And can you access your shares from other pc's?
[17:46] <eXistenZe> it is running
[17:46] <eXistenZe> gonna test the shares...
[17:48] <eXistenZe> nope... no shares
[17:49] <lordievader> eXistenZe: You cannot connect, or no shares configured?
[17:51] <eXistenZe> ok... gonna need n00b english here for that lordievader
[17:52] <lordievader> eXistenZe: Well you can get an error that it cannot connect to your server. Or you can get an empty screen since no shares are defined yet.
[17:54] <eXistenZe> oh... can't find the server
[17:55] <eXistenZe> since it's a windows pc I can only check if it connects to the ip or not
[17:55] <lordievader> eXistenZe: On the smb host what is the output of 'sudo netstat -tulpn|grep smb'?
[17:57] <eXistenZe> https://paste.kde.org/p1estu4j8
[17:58] <lordievader> eXistenZe: Do you run a firewall?
[17:58] <eXistenZe> nope
[17:59] <lordievader> Hmm, then you should be able to connect to the smb server.
[18:06] <eXistenZe> wait
[18:06] <eXistenZe> now theres a _MSBROWSE_ smb server
[18:06] <eXistenZe> and it has this machines IP, so it is samba
[18:07] <eXistenZe> but it only has a folder with my printer name?
[18:10] <lordievader> eXistenZe: That is likely. A fresh samba server has no shares configured. Configure them in /etc/samba/smb.conf
[18:10] <eXistenZe> I thought the shares I define in dolphin where also shown
[18:17] <eXistenZe> nice... working
[18:18] <eXistenZe> but I still can't acess my workgroup in dolphin (worng password)
[18:22] <lordievader> Did you give your user an smb password?
[18:24] <eXistenZe> yes.
[18:24] <eXistenZe> and it works for other pcs
[18:26] <eXistenZe> including KVM (just figured the problem: it was not using the default IP 10.0.2.2, but a normal 192.x..x.x, just tiped the assigned dns server IP it was connecting to)
[18:33] <eXistenZe> still  getting "Access denied to smb://myuser@workgroup/."
[18:34] <lordievader> What about 'smb://localhost'?
[18:36] <eXistenZe> it works
[18:36] <eXistenZe> it's just the workgroup that's got messed up
[18:37] <lordievader> eXistenZe: No, you use the workgroup as if it is an hostname.
[18:38] <eXistenZe> ?
[18:38] <lordievader> The format is smb://<user>@<hostname>
[18:39] <eXistenZe> but why is there a login to access a workgroup?
[18:39] <lordievader> ?
[18:40] <eXistenZe> I am asked the login when I open the Workgroup, not the individual smb machines/servers
[18:40] <lordievader> Perform an nslookup on the workgroup.
[18:43] <eXistenZe> step by step?
[18:44] <lordievader> nslookup <workgroup>
[18:46] <eXistenZe> weird
[18:46] <eXistenZe> https://paste.kde.org/pirvdgfii
[18:46] <lordievader> Hmm, no idea what it is doing...
[22:03] <runlau> join #ubuntu
[22:34] <regedit> where can i view Kubuntu's menu/launcher log
[22:34] <regedit> log or command history
[22:35] <regedit> need to figure out why its not launching a program with the arguments I am supplying in Edit Applications
[23:28] <regedit> halp!
[23:28] <regedit> i accidentally my /etc/default/grub :(
[23:31] <regedit> i have a whole UEFI setup, does that mean that file had special non-default settings in it?
[23:32] <Unit193> Shouldn't, sudo cp /usr/share/grub/default/grub /etc/default/
[23:34] <regedit> Unit193: thank you kind sire!
[23:36] <regedit> Unit193: i also had dual boot with the UEFI... still no biggie?
[23:36] <regedit> Windows
[23:37] <regedit> it had 3 options: ubuntu (default), advanced options for ubuntu, and Windows boot manager /dev/sd?)
[23:37] <Unit193> update-grub, see what it says.
[23:38] <Unit193> That file is just defaults, /etc/grub.d/ contains the scripts to detect that stuff, and /boot/grub/grub.cfg was the actual generated file.
[23:38] <regedit> Unit193: i see mention of all above options, so that means it's all good?
[23:38] <Unit193> regedit: That should mean it's all good™
[23:38] <regedit> :D ok
[23:52] <regedit> i am suffering from some Nvidia issues which are apparently fixed in a future driver version
[23:52] <regedit> is it possible to install such?
[23:53] <regedit> current Nvidia driver version: 346.59. Later version: 352.21