[01:21] <maruf> assalamualaikum
[03:13] <jarkko> my system says that new version of kubuntu is available - i am using 13.10
[03:13] <jarkko> ??
[03:15] <jarkko> how is this possible
[03:15] <jarkko> sudo apt-get update, upgrade dist-upgrade none shows new packages
[06:17] <DarthFrog> jarkko:  That's because you need to do "sudo do-release-upgrade" instead of apt-get.
[06:29] <jarkko> well i solved that one already
[06:50] <jussi> jarkko: how did the upgrade go?
[06:51] <lordievader> Good morning.
[06:53] <jarkko> i just dont understand why kubuntu said that i have new KUBUNTU version
[07:24] <31NAAA2T8> Hi, kubunters!
[07:30] <lordievader> Good morning 31NAAA2T8
[10:41] <esing> Hi, should I use kde's autostart gui to enable a service on boot or should I add it to /etc/rclocal or even somewhere else?
[10:59] <apachelogger> esing: depends on when you want it to start
[10:59] <apachelogger> kde's austostart gui will usually be best for things that only need to run when one is logged in
[11:00] <esing> apachelogger※ I chose /etc/rc.local because I don't need a UI for the service
[11:00] <apachelogger> esing: it's regardless of whether it needs a UI
[11:00] <apachelogger> kde's autostart is only executed when one logs in... rc.local is started at init
[11:01] <esing> I see, in my case it doesn't matter whether it starts at init or later
[11:01] <apachelogger> also unless you define a user rc.local will be executed as root, which may be a bad thing (again, depending on what service you want to run)
[11:02] <apachelogger> esing: kde's autostart should be preferred then because of the root thing
[11:02] <esing> apachelogger※ I thought rc.local is predefined to be executed as root?
[11:03] <esing> Oh I see what you mean
[11:03] <esing> The service requires to be started as root anyways
[11:05] <apachelogger> esing: ah, use rc.local then
[11:05] <apachelogger> it's a silly thing if it requires to be started as root though :P
[11:06] <esing> apachelogger※ apache2 or other webservers have to be run as root too iirc
[11:07] <esing> And the service I need in this case is 'knockd' which lets me open ports through iptables remotetly
[11:08] <apachelogger> esing: apache most certainly doesn't need to be run as root, possible started to get the port open, definitely not run though
[11:09] <apachelogger> I should know, I log the apaches ;)
[11:09] <esing> Heh :)
[11:58] <BluesKaj_> Hiyas all
[12:21] <esing> I tried to start a service on autostart with /etc/rc.local -> /etc/init.d/knockd start and with kde autostart as a script (/home/user/knockd.sh): #!/bin/sh /etc/init.d/knockd start, but both ways don't work for this service. I read that there's a bug with the services autostart, but if I run /etc/init.d/knockd start after bootup it works, so I wonder why it's not working when I put it in kde's autostart which executes it also after bootup?
[12:21] <esing> *script
[12:31] <BluesKaj> esing. does knockd also reside in /home , perhaps autostart sees in in init.d and assumes it's on , I know that the dropboxd script works in autostart without residing in init.d or /etc/local
[12:35] <esing> BluesKaj, Knockd resides not in /home. I only put the script from which I call /etc/init.d/knockd start into /home
[12:36] <BluesKaj> esing. did you check hidden files ?
[12:36] <esing> Yes
[12:37] <BluesKaj>  /usr/bin ?
[12:39] <esing> BluesKaj, Yes, there is its client 'knock'
[12:41] <BluesKaj> esing. but knockd is the script , so where does it reside by default ?
[12:44] <esing> BluesKaj, Its conf files are in /etc/knockd.conf /etc/default/knockd and /etc/init.d/knockd
[12:45] <esing> BluesKaj, And here: /usr/sbin/knockd
[12:46] <BluesKaj> esing set autostart to point to /etc/default/knockd , or /usr/sbin/knockd to see if that works
[12:49] <esing> BluesKaj, I put /usr/sbin/knockd into kde's autostart and in rc.local and both didn't work. /etc/default/knockd is just anoother conf file
[12:51] <BluesKaj> esing. system settings > startup&shutdown>autostart ?
[12:57] <esing> BluesKaj, Yes, there
[12:58] <esing> I added it as a script to the location /usr/sbin/knockd
[12:58] <esing> I added it also a program, but on the next reboot it vanishes from the autostart program list
[12:58] <esing> +as
[13:00] <BluesKaj> add it as a script only , if that's what it is
[13:03] <esing> It's actually a binary program
[13:04] <esing> But if I start its service I use the paramter /etc/init.d/knockd start
[13:36] <esing> BluesKaj, It works if I run it with sudo and set sudo /etc/init.d/knockd start without password in sudoers
[13:37] <esing> So I wonder how I can run root scripts without sudo no password in kde's autostart
[13:43] <esing> But I guess, since root owns the places /etc/init.d/knockd and /usr/sbin/knockd anyways it should be safe enough
[13:51] <pic01> in Kubuntu 12.04 how can I change my username?
[15:29] <calwig> !kgpg
[15:29] <calwig> guidelines to set it up anyone?
[18:17] <Tm_T> uh, is the network systray icon supposed to open some kind of configuration dialog or something where I could choose for example wifi networks? clicking the icon does nothing here
[18:18] <Tm_T> Kubuntu 13.10 with KDE SC 4.11.3
[18:18] <Tm_T> I think
[18:30] <BluesKaj> add widgets in the panel , network , network manager should appear , choose that , Tm_T
[18:38] <Tm_T> BluesKaj: yeah I have that, exactly the icon I was talking about (:
[19:00] <Dutchman> Tm_T: what happens if you right-click on the icon?
[19:08] <Tm_T> Dutchman: gives me an option to configure what is shown
[19:12] <Dutchman> Tm_T: I'm not at all sure why it's not working normally, but perhaps you can try clicking on "Defaults" on the lower part of the config dialog, see if that brings it back.
[19:12] <Dutchman> Re-set it basically.
[19:13] <Tm_T> oh that I'm not going to do, it seems that the network manager widget doesnt work here on systray
[19:15] <Dutchman> Tm_T: I have the same version, 4.11.3, and it does work here, so I can't see it being the widget. Thought maybe resetting if might bring back the left-click menu.
[19:18] <soee> Riddell, i just checked telepathy
[19:18] <soee> sorry
[19:18] <Dutchman> Tm_T: If you right-click, and open the network management settings dialog, does it show anything in the right side panel, under "Details to Show"?
[19:22] <Tm_T> Dutchman: http://www.tm-travolta.net/shots/nm-applet1.png
[19:22] <Tm_T> removing and readding widget makes no difference
[19:28] <Dutchman> Tm_T: Well, your settings look right, so I have no idea past that what could be wrong. I have seen widget problems in the past with themes, have you tried a different Plasma theme, just to test?
[19:36] <SJr> Kubuntu 13.10, worth it?
[19:38] <soee> its priceless
[19:44] <Crell> Hi folks.  I've just updated to 13.10 on my laptop and I'm working out the kinks.
[19:45] <Crell> One kink is that the taskbar at the bottom of the screen is now black.
[19:45] <Crell> It's completely black, with the buttons and icons and such on top of that, which makes them really hard to read.
[19:45] <kaddii> anyone know any good benchmarking tools for ubuntu... wanna see how a laptop handles heat
[19:45] <Crell> Is that a render issue, or a setting, or...?
[19:46] <soee> Crell, this shouldnt happen
[19:46] <soee> maybe gfx issue ?
[19:46] <Crell> I agree, it shouldn't. :-)
[19:46] <Crell> That's what I am trying to find out.
[19:46] <soee> try do disable/enable effects
[19:46] <soee> ctrl+shift+f12
[19:47] <Crell> That seems to do nothing.
[19:47] <Crell> I don't have many effects enabled in the first place.
[19:47] <kaddii> ah wait.. sorry guys... the live-usb actually runs gnome
[19:47] <kaddii> anyone know any good benchmarking tools for ubuntu... wanna see how a laptop handles heat
[19:48] <soee> Crell, maybe try to remove panel and add it again
[19:48] <Crell> Hm.
[19:48] <Crell> It's the entire plasma bar, or whatever it's called these days.
[19:49] <Crell> Oh good.  Now I can't get to the settings menu because the damned calendar popup is in the way, and is covering the clock so I can't minimize it again. :-)
[19:50] <Crell> Ah ha!
[19:50] <soee> :)
[19:50] <Crell> Yes, remove and re-add the default seems to have worked.
[19:50] <Crell> 'course, now I have to re-customize it...
[19:50] <Crell> And now it's a fugly light gray.
[19:50] <soee> its probalby you had some settings from previous installation
[19:50] <Crell> And they didn't upgrade cleanly?
[19:50] <soee> enable effects
[19:51] <soee> rename .kde folder
[19:51] <soee> logout/login and setup everything from scratch
[19:51] <Crell> The entire .kde folder?
[19:51] <soee> just rename it so it will be recreated
[19:51] <Crell> Ugh.  I thought updates were supposed to be stable enough these days that I don't need to reset everything.
[19:52] <Crell> The .kde folder contains a lot of application settings I don't want to redo.
[22:16] <Juan32> hello, any to talk?
[22:20] <Juan32> hola