[07:32] <lordievader> I found a bug with the touchpad disable hotkeys, they only work if Sys config -> Input Devices -> Touchpad -> Enable/Disable Touchpad is open, if that is closed the shortcut no longer works.
[07:33] <lordievader> To what application/package do I address this bug?
[07:46] <apachelogger> lordievader: https://bugs.kde.org/enter_bug.cgi?product=Touchpad%20KCM&format=guided
[07:47] <lordievader> apachelogger: Thank you :)
[08:51] <shadeslayer> apachelogger: http://imgur.com/KiuBS9K
[08:52] <shadeslayer> in muon discover
[08:58] <shadeslayer> and go and test utopic alpha 1
[09:15] <shadeslayer> WARNING: This image is OVERSIZED. This should never happen during milestone testing.
[09:15] <shadeslayer> :(
[09:29] <mcstr_> hi guys! i posted this question yesterday already and also posted it on launchpad.  i am running kubuntu 14.04 and have additionally added kde project neon via the ppas. is there a way to use the application settings from my apps in kubuntu 14.04 also in kde project neon? like the channels in quassel or the email accounts.  what folder do i have to copy for this?
[09:31] <yofel> that's mostly the xdg folders like .config or .local/share, see what the XDG_* environment variables are set to for the places neon5 looks
[09:31] <yofel> quassel is in .config, email should be controlled by akonadi which is too
[09:32] <mcstr_> hm where can i check the xdg environment variables for neon5?
[09:33] <yofel> when you run neon5, just open konsole and run 'env'
[09:33] <shadeslayer> it will most likely be /home/shadeslayer/.project-neon5-kde/something
[09:33] <yofel> mcstr_: they are set by some environment.rc file in /opt/project-neon5/share/project-neon5 IIRC (paths and names might not be entirely correct here)
[09:33] <mcstr_> indeed i have it in /home/macstar/.project-neon5-kde
[09:34] <mcstr_> in this i have a-.config folder....
[09:34] <mcstr_> can i try to overwrite this config folder with the config folder i have in my home directory?
[09:34] <mcstr_> backing up first ofc
[09:34] <yofel> yes
[09:34] <shadeslayer> I think if you just copy it over, it should be fine
[09:34] <mcstr_> yep folder structur inside looks the same
[09:35] <mcstr_> gonna try thx
[09:41] <shadeslayer> what the heck is back http://imgur.com/X5wBZGf
[09:42] <mcstr_> no luck here
[09:42] <mcstr_> env output looks like this http://goo.gl/6RqjVr
[09:43] <mcstr_> shit
[09:43] <mcstr_> i think i am to blame
[09:43] <mcstr_> its config not .config in the project neon folder
[09:43] <mcstr_> :/
[09:43] <shadeslayer> XDG_CONFIG_DIRS=/opt/project-neon5/etc/xdg:/etc/xdg/xdg-project-neon5:/etc/xdg:/etc/xdg
[09:43] <shadeslayer> wat
[09:44] <shadeslayer> aha
[09:44] <mcstr_> brb
[09:44] <shadeslayer> mcstr_: you're right
[09:45] <lordievader> shadeslayer: What does that back do? Go back to the BIOS? /me is getting curious
[09:47] <shadeslayer> lordievader: http://imgur.com/S0aTfUr
[09:48] <lordievader> Pff, lovely.
[09:49] <mcstr> yep that was it
[09:49] <mcstr> thanks a lot guys
[09:50] <mcstr> and wow it feels fast :O
[09:55] <mcstr> last thing i need to have working is the akonadi server..... its not running therefore i cant use kmail/kontact...
[09:56] <shadeslayer> you can't use akonadi on frameworks yet
[09:56] <shadeslayer> IDK why
[09:56] <mcstr> oh okay
[09:56] <shadeslayer> but it simply doesn't work
[09:56] <mcstr> no worries
[09:56] <mcstr> as long as it works in the final im happy :p
[09:56] <mcstr> everything else looks damn impressive by now
[10:09] <apachelogger> shadeslayer: it's a bug
[10:10] <apachelogger> also technically that would in fact attempt to go back if that was a submenu
[10:10] <apachelogger> alas, it is not, so I doubt that should be there xD
[10:10] <shadeslayer> apachelogger: yep, new syslinux and what not
[10:10] <shadeslayer> no OEM menu too
[10:10] <shadeslayer> all reported
[10:10] <shadeslayer> installer crashes with non english lang :(
[10:11] <shadeslayer> 1334199
[10:11] <shadeslayer> er
[10:11] <shadeslayer> bug 1334199
[10:11] <apachelogger> don't find no branch on lunchpad for the new thing for whatever reason
[10:11] <apachelogger> they are hiding it from me
[10:13] <shadeslayer> new thing?
[10:13] <shadeslayer> the Qt5 installer?
[10:14] <shadeslayer> apachelogger: do you reckon 1334199 is a blocker for Alpha 1 ?
[10:15] <apachelogger> shadeslayer: the new sylinux
[10:15] <apachelogger> since you can install in english I don't think that's much blocky
[10:16] <shadeslayer> kk
[10:16]  * shadeslayer lazily looks at firefox
[10:38] <shadeslayer> agateau: ping
[10:38] <shadeslayer> agateau: I thought this was fixed http://imgur.com/Iy5735j
[10:38] <shadeslayer> the quit button
[10:55] <shadeslayer> Riddell: wat http://launchpadlibrarian.net/134020427/ubiquity_2.13.14_2.13.15.diff.gz
[11:05] <shadeslayer> :O
[11:05] <shadeslayer> wat
[11:05] <shadeslayer> https://launchpad.net/debian/+source/kde4libs
[11:06] <shadeslayer> that's pretty neat
[11:06] <shadeslayer> I can also do http://pad.lv/d/kde4libs now :3
[11:06] <shadeslayer> agateau: mind poking https://code.launchpad.net/~agateau/ubiquity/kde-fix-broken-sidebar-layout-on-greeter/+merge/216365
[11:07] <agateau> shadeslayer: what do you mean with "poking"?
[11:07] <agateau> shall I ping Riddell about it?
[11:07] <agateau> just did it :)
[11:08] <shadeslayer> heh
[11:08] <shadeslayer> agateau: well more like, maybe not use the hack
[11:09] <agateau> shadeslayer: i don't think this hack is critical
[11:09]  * Riddell is travelling today
[11:10] <shadeslayer> ok
[11:10] <shadeslayer> Riddell: coming via car?
[11:10] <shadeslayer> or Flight?
[11:10] <shadeslayer> and I thought you were arriving tomorrow
[11:10] <Riddell> por avión
[11:11] <Riddell> 10 a las noches
[11:11] <shadeslayer> aha
[11:12] <shadeslayer> Riddell: cya tomorrow :)
[11:12] <shadeslayer> Riddell: where are you staying though?
[11:14] <Riddell> shadeslayer: dunno, I was hoping someone would be in the office this evening to let me in
[11:15] <Riddell> d_ed said he would be I think
[11:15] <shadeslayer> ok, if required, I can be there too
[11:29] <ovidiu-florin> hello world
[11:30] <ovidiu-florin> Riddell: where can I find a list of what I have to do to apply for membership?
[11:30] <Riddell> ovidiu-florin: http://community.kde.org/Kubuntu/Membership
[11:31] <ovidiu-florin> Riddell: The Kubuntu Romania site is also down
[11:31] <ovidiu-florin> any news on that subscription?
[11:37] <Riddell> ovidiu-florin: not had a chance yet sorry :(
[11:38] <ovidiu-florin> so you said you're moving?
[11:38] <ovidiu-florin> why ?
[11:40] <Riddell> I like messing up the geopolitics of europe, scotland is a done deal, time to have fun with the catalunians
[11:41] <sgclark> lol
[11:55] <ovidiu-florin> :)
[12:37] <BluesKaj> 'Morning folks
[12:37] <Riddell> "Rohan Garg (rohangarg) renewed their own membership in the Kubuntu Members" yay shadeslayer still loves us!
[12:38] <soee> hi BluesKaj
[12:39] <BluesKaj> hi soee
[12:43] <d_ed> Riddell: I'll be in the office tonight
[12:43] <d_ed> Riddell: what are your sleeping arrangements?
[12:43] <d_ed> Riddell: are you out here forever?
[12:48] <Riddell> d_ed: yep
[12:48] <Riddell> no arrangements yet, I'm hoping some kind person will offer me a sofa
[12:51] <Riddell> or the office has plenty of space and a hose in it
[13:17] <Riddell> hi mustafa_muhammad 
[13:19] <mustafa_muhammad> Hello Jonathan
[13:20] <Riddell> mustafa_muhammad: running Kubuntu in Iraq?
[13:20] <mustafa_muhammad> Yup, distro-hopping in Iraq
[13:20] <mustafa_muhammad> Testing neon5 and plasma 5 now
[13:21] <mustafa_muhammad> neon5 running fine(except some crashes, reported)
[13:22] <mustafa_muhammad> but Kubuntu Utopic couldn't login from the kubuntu-next ppa
[13:35] <mustafa_muhammad> When I login, I get "Could not start D-Bus, can you call qdbus?"
[13:35] <sgclark> that is the problem I have, I am looking into it
[13:36] <sgclark> lightdm seems to be the fail point
[13:36] <mustafa_muhammad> So, try sddm?
[13:36] <mustafa_muhammad> I'll give it a shot
[13:36] <sgclark> I just packaged it, have not yet tested
[13:38] <shadeslayer> doesn't sound like a sddm/lightdm problem
[13:38] <shadeslayer> more like a qtchooser issue
[13:38] <yofel> is qdbus-qt5 installed? ^^
[13:39] <sgclark> yeah it was
[13:42] <apachelogger> qt5-default as well
[13:53] <shadeslayer> anyone want to test http://iso.qa.ubuntu.com/qatracker/milestones/317/builds/70677/testcases/1301/results
[13:55] <sgclark> I will here in a bit
[13:55] <mustafa_muhammad> apachelogger: qt5-default was not installed, now I installed it and logged in, no problems anymore
[13:56] <mustafa_muhammad> thanks
[13:56]  * sgclark adds to depends
[13:57] <mustafa_muhammad> sgclark: try installing qt5-default, worked for me
[13:57] <sgclark> will do thank you
[14:12] <shadeslayer> sgclark: please don't add qt5-default to runtime depends
[14:12] <shadeslayer> because qdbus is supposed to be a drop in replacement
[14:12] <soee_> hey, so sddm is now wvailable for 14.10 ?
[14:12] <shadeslayer> so you can install the Qt4 version as well
[14:12] <shadeslayer> soee_: not yet
[14:13] <shadeslayer> I don't see us switching to it in 14.10 tbh
[14:13] <shadeslayer> because at the very least ubiquity will break
[14:13] <shadeslayer> or rather, ubiquity-dm
[14:13] <soee_> shadeslayer: it wont be available even as 'unoffical' option
[14:13] <shadeslayer> soee_: dunno, maybe
[14:13] <soee_> ok, thank you
[14:13] <shadeslayer> no plans for it yet
[14:13] <shadeslayer> maybe just for plasma 5
[14:15] <apachelogger> shadeslayer: it would have to be there for plasma5 as its considered part of the workspace experience
[14:16] <apachelogger> which is why I told Quintasan to hurry it along like 70000 weeks ago :@
[14:16] <sgclark> plasma-desktop will not start without it, therefore broken, how am I to resolve tht?
[14:18] <sgclark> I packages sddm, it is in next utopic
[14:18] <sgclark> packaged*
[14:19] <shadeslayer> apachelogger: is it? 
[14:19] <shadeslayer> I don't think so
[14:19] <shadeslayer> but anyway
[14:19] <shadeslayer> breaks ubiquity-dm
[14:20] <apachelogger> shadeslayer: I am not sure it does, it probably will need to be noop when ubiquity is supposed to start
[14:20] <shadeslayer> yes, noop = broken for me :P
[14:20] <shadeslayer> loss of features etc
[14:20] <apachelogger> what?
[14:20] <apachelogger> if you start livesession
[14:21] <apachelogger> the sddm upstart/sytemd unit shouldn't do no nothing
[14:21] <apachelogger> so that ubiquity can fire up lightdm with ubiquity greeter
[14:21] <sgclark> shadeslayer: with that said, leaving off qt5-default as depend leaves a system that cannot be logged into which I see as a grand form of broken
[14:21] <apachelogger> when started after install sddm will do its magic
[14:21] <shadeslayer> sgclark: no, qt5-default is the wrong depend
[14:21] <shadeslayer> you should depend on qdbus
[14:21] <shadeslayer> not qt5-default
[14:22] <apachelogger> actually
[14:22] <apachelogger> something needs to depend on qtchooser
[14:22] <apachelogger> which is qhere qt5-default comes in :P
[14:22] <sgclark> I had qdbus, still broken
[14:22] <apachelogger> question is why qmake doesn't
[14:23] <apachelogger> ah
[14:23] <sgclark> qt5-default and viola I have a desktop and I am very happy now
[14:23] <apachelogger> sgclark: are you sure qt5-qdbus was installed?
[14:23] <shadeslayer> qmake is blacklisted I think
[14:23] <apachelogger> sgclark: the actual package qt5-qdbus
[14:24] <apachelogger> or actually, please paste your /var/log/dpkg.log
[14:24] <shadeslayer> apachelogger: well, it shouldn't really matter, this is the whole QT_SELECT=4/5 fiasco
[14:24] <apachelogger> because qt5-default would simply have dragged in what was missing, it wasn't the actually missing bit as it is an empty package
[14:24] <shadeslayer> in startkde
[14:24] <sgclark> apachelogger: I cannot even get into that system. grub seems to have vanished and cannot get to rescue even
[14:24] <apachelogger> shadeslayer: no, because it would default to qmake5 in this scenario
[14:25] <apachelogger> the only way you get a defunct qmake with qt5 installed is if the actual binary is not there
[14:25] <apachelogger> sgclark: https://help.ubuntu.com/community/LiveCdRecovery
[14:25] <apachelogger> http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd
[14:26] <shadeslayer> apachelogger: actually, I have both qmake qt4/5 installed, it defaults to 4
[14:26] <apachelogger> sgclark: actually you could just livecd, mount whatever partition contains /var and paste me the log :P
[14:26] <shadeslayer> ^^
[14:26] <apachelogger> shadeslayer: only if you misconfigured it
[14:26] <shadeslayer> nope
[14:26] <shadeslayer> I merely installed both
[14:26] <apachelogger>  readlink /usr/lib/x86_64-linux-gnu/qtchooser/default.conf 
[14:26] <apachelogger> ../../../share/qtchooser/qt5-x86_64-linux-gnu.conf
[14:27] <shadeslayer> I have no /usr/lib/x86_64-linux-gnu/qtchooser/default.conf
[14:27] <shadeslayer> because I have no default package
[14:27] <apachelogger> oh, that's from qt5-default
[14:27] <shadeslayer> yep
[14:27] <apachelogger> you know what
[14:28] <apachelogger> let's sneakily remove qtchooser :P
[14:28] <apachelogger> shadeslayer: oh perhaps that is why only some systems had a problem with qmake4 vs. 5
[14:29] <apachelogger> that's funny though, it defaults to qmake4, unless you have qt5-default, unless you have it configured... it still won't work though unless you have the correct package for your architecture
[14:30] <apachelogger> it's much better than having to rename the binary to qmake5 xD
[14:30] <shadeslayer> :p
[14:30] <apachelogger> shadeslayer: it appears you are right, unless qt5-default is installed it will default to qmake4
[14:31] <apachelogger> so it is the inverse issue of the previous issue \o/
[14:33] <apachelogger> wait that's weird as well
[14:33] <apachelogger> sgclark: I think qtchooser will need fixing for this
[14:37] <apachelogger> the problem is... in plasma current when using qdbus with qt5-default installed it would have used qdbus-qt5 which might not have been installed; this kind of made sense even considering it is still a bug with qtchooser having insufficient lookup logic... now with plasma next OTOH you cannot ever hope to use qdbus5 unless qt5-default is installed (which is a dev package of sorts) as it will always attempt to start qmake4 which is never 
[14:37] <apachelogger> there
[14:38] <sgclark> ahh
[14:38] <shadeslayer> sgclark: mind reverting your commit then?
[14:38] <apachelogger> actually my analysis was still not correct, if you have both qtcore4 and qtcore5 installed you cannot use qdbus5 unless you have qt5-default installed
[14:39] <shadeslayer> you can
[14:39] <apachelogger> anyone ordered a turd?
[14:39] <sgclark> but that breaks it, gosh I am lost 
[14:39] <shadeslayer> QT_SELECT=5 qdbus
[14:39] <apachelogger> yeah
[14:39] <shadeslayer> voila, it'll wor
[14:39] <shadeslayer> *work
[14:39] <apachelogger> the point of qtchooser somewhat was to not having to do that
[14:39] <apachelogger> so the fact that you need to do it anyway defeats the point
[14:41] <shadeslayer> funnily, half of neon depends on qdbus
[14:41] <shadeslayer> which is the qt4 package
[14:41] <apachelogger> no
[14:41] <apachelogger> shadeslayer: u talking about neon4?
[14:41] <shadeslayer> 5
[14:41] <apachelogger> neon5 has its own qt
[14:41] <apachelogger> straight qt build doesn't have qtchooser
[14:42] <shadeslayer> apachelogger: http://paste.kde.org/pfqiulxvm
[14:42] <apachelogger> ah
[14:42] <apachelogger> that is peculiar
[14:43] <shadeslayer> sgclark: it was broken because qtchooser is broken, however qt5-default forces Qt5 as the default everywhere
[14:43] <shadeslayer> qt5-default just papers over the issue
[14:44] <shadeslayer> it doesn't actually solve it ( or maybe it partially does, by pulling in qdbus-qt5 )
[14:44] <apachelogger> shadeslayer: that's through weird dep chain though, there is no direct dep on qdbus
[14:44] <shadeslayer> apachelogger: yaeh I guessed as much
[14:45] <apachelogger> shadeslayer: run -o Debug::pkgProblemResolver=true plz
[14:46] <shadeslayer> apachelogger: http://paste.ubuntu.com/7700753/
[14:46] <apachelogger> Broken project-neon5-qtcurve:amd64 Depends on libkio5 [ amd64 ] < 4:4.13.2a-0ubuntu0.1 > ( libs ) (>= 4:4.3.4)
[14:46] <apachelogger> all ur fault
[14:47] <apachelogger> Broken project-neon5-kauth:amd64 Depends on libpolkit-qt-1-1 [ amd64 ] < 0.103.0-1ubuntu1 > ( libs ) (>= 0.99.0)
[14:47] <apachelogger> that looks wrong though
[14:47] <shadeslayer> quite wrong
[14:47] <apachelogger> qtcurve I also don't get much
[14:47] <shadeslayer> I know why
[14:48] <shadeslayer> we're buiding with  kdelibs5-dev
[14:48] <xnox> shadeslayer: sgclark: soee_: it's a bug in software if qt5-defaults / qt4-defaults changes anything. Especially for ubiquity.
[14:48] <sgclark> I reverted my change, is there a way to set QT_SELECT=5 qdbus on install ? so it is not broken out of the box?
[14:49] <xnox> shadeslayer: sgclark: soee_: which we can trivially fix by being explicit about qt version if we have to in ubiquity.
[14:49] <xnox> which would be my preference.
[14:49] <shadeslayer> sgclark: again, wrong way to approach the solution
[14:50] <shadeslayer> I'd do it in startkde
[14:50] <shadeslayer> like we currently do it for KDE SC
[14:53] <sgclark> well off topic a bit, while I can login in now, it still is not working, everything is black
[14:55] <shadeslayer> apachelogger: https://notes.kde.org/p/kubuntu-next
[14:55] <shadeslayer> plz review
[14:55] <shadeslayer> ScottK: ^^ bullet points for easier understanding of deliverables
[15:03] <apachelogger> I read the bullet points
[15:03] <apachelogger> they were bullety
[15:04] <apachelogger> shadeslayer, sgclark: xnox: this needs fixing in qtchooser, it's undesirable to patch every invocation of qdbus to explicitly select a version
[15:05] <shadeslayer> true enough
[15:05] <shadeslayer> if everything in that document reads fine to you guys, I'll send it tomorrow morning
[15:15] <shadeslayer> sgclark: http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/sddm/view/head:/debian/control < all them themes are bunched together :(
[15:16] <shadeslayer> sgclark: plus you install no pam files
[15:16] <shadeslayer> or init files
[15:21] <shadeslayer> apachelogger: isn't https://trello.com/c/JH9j9mH5 done?
[15:21] <shadeslayer> override_dh_shlibdeps:
[15:21] <shadeslayer>          $(overridden_command) -- -xbaloo -xkde-runtime -xkdepim-runtime
[15:21] <shadeslayer> from baloo debian/rules
[15:27] <sgclark> shadeslayer: ok split out themes? did not see any of these pam or init files you speak of, will take a look a bit later
[15:28] <shadeslayer> sgclark: well, the pam files shipped with sddm are kaput for Ubuntu
[15:28] <shadeslayer> sgclark: did you even check if your sddm package worked?
[15:28] <shadeslayer> I can't imagine it working :P
[15:28] <sgclark> shadeslayer: I stated that no it has not been tested.
[15:29] <shadeslayer> hm, it only says that it needs review, I thought you had it working
[15:29] <sgclark> All I see is blotchy black on the machine I am trying to set up to test this stuff, not a good day. before that all the dbus stuff
[15:30] <sgclark> sorry I was not clear, defined etc.
[15:32] <sgclark> shadeslayer: this package did not create a debian/tmp (why I did not create install files) what did I miss?
[15:35] <shadeslayer> sgclark: debhelper does not create debian/tmp for control files with just one package
[15:36] <sgclark> ah ha, ok so will when I split themes, thanks
[15:40] <shadeslayer> sgclark: please use my branch as a base
[15:40] <shadeslayer> if you're working on SDDM
[15:41] <sgclark> you can have it back sorry, did not realize you were working on it
[15:41] <shadeslayer> sort of, I was thinking of doing it tomorrow
[15:41] <shadeslayer> sanitizing the packaging
[15:41] <shadeslayer> and having something shippable
[15:41] <shadeslayer> but if you have time, go for it
[15:57] <sgclark> shadeslayer: well at this point I need a working test system, which so far is not going well
[16:02] <yofel> shadeslayer: notes look fine
[17:22] <ShalokShalom> hi there
[17:22] <ShalokShalom> can i report a packaging bug here, please ?
[17:22] <yofel> ShalokShalom: preferably file a bug with apport / on launchpad, but what's up?
[17:46] <ShalokShalom> yofel: mpd is a GUI for mpd and mpd isnt a dependency for cantata
[17:47] <ShalokShalom> yofel: mpd is a GUI for cantata and mpd isnt a dependency for cantata
[17:53] <ShalokShalom> yofel: cantana dont work without mpd and mpd isnt a dependency from cantana. (my english is horrible)
[17:57] <yofel> ShalokShalom: sorry was away. I'm not really familiar with mpd, and the new version in utopic-proposed does at least suggest mpd so maybe that's enough (I usually trust debian to know what they're doing)
[17:57] <ShalokShalom> its not enough
[17:57] <ShalokShalom> i already check this with the help from BluesKaj
[17:58] <ShalokShalom> Cantata is a GUI for mpd
[17:58] <ShalokShalom> try it ;)
[18:00] <yofel> hm, true, this is useless..
[18:04] <yofel> ShalokShalom: well, I can see that it might want to at least recommend it, but considering that you might have mpd running on another pc suggests isn't too wrong
[18:05] <yofel> if you already have mpd running somewhere, starting another instance on your system is probably not what you want
[18:07] <yofel> ShalokShalom: yeah, that was already discussed in debian bug 740299
[18:16] <ShalokShalom> yofel: Why "or a recommendation and why [Normal] ?  
[18:16] <ShalokShalom> Its breaks the whole App ?
[18:16] <yofel> not if it's running somewhere else
[18:16] <ShalokShalom> For each end user
[18:16] <ShalokShalom> How many people aim to use it as a music client on the desktop ?
[18:17] <ShalokShalom> And how should one of these end user know, why cantana dont work ?
[18:18] <tsimpson> it may be a case for diverging from upstream, maybe
[18:19] <yofel> when I started cantata, on the second configuration screen it asked me to connect to mpd. I would expect that someone that wants to use an mpd client might wonder where mpd is if cantata can't connect to it
[18:19] <yofel> it is true that our package in trusty does not suggest mpd, so that might be worth fixing
[18:20] <ShalokShalom> ok, can you suggest this ?
[18:22] <yofel> I'll file a bug about it, maybe I'll have some time over the weekend to fill out the SRU paperwork
[18:33] <ShalokShalom> yofel: thanks a lot :)
[19:21] <beav_> anybody know how to upload GTK app tar ball onto ubuntu? it's for gnome or kde.
[19:21] <beav_> It's graphical interface not shell, thanks in advance.
[19:23] <beav_> I want to distribute the application and make it accessable for ubuntu users to download as an open source project
[20:25] <BluesKaj> hmm, no upgrades in the 14.10 repos today...is there a freeze on?
[20:26] <BluesKaj> anyway time to give this a rest ..
[20:28] <shadeslayer> yep