[02:04] <dougl> xserver-xorg-video-all : Depends: xserver-xorg-video-nouveau but it is not installed - I installed nvidia drivers, how can I remove xserver-xorg-video-all ?
[02:05] <dougl> err can I
[02:05] <dougl> ?
[02:08] <Riddell> dougl: no X experts here, try asking in #kubuntu, #ubuntu or #ubuntu-x
[02:18] <dougl> Riddell, thanks :)
[03:57] <kubotu> ::runtime-bugs:: [1298951] kwalletd crashed with SIGABRT in __GI_raise() @ https://bugs.launchpad.net/bugs/1298951 (by Gustavo Boksar)
[04:58] <Kalidarn> btw that issue with the device manager is still in KDE 4.12.97
[05:04] <Kalidarn> is there some reason we are not using KDE 4.13 and are using betas of it?
[05:05] <Kalidarn> i was under the assumption KDE 4.12.X were betas of of KDE 4.13
[05:10] <jussi> Kalidarn: isnt 4.13 planned for release next week? 
[05:10] <jussi> http://techbase.kde.org/Schedules/KDE4/4.13_Release_Schedule
[05:11] <Kalidarn> i was sure it was already released
[05:11] <Kalidarn> was sure i was using it in 3.10 with the backports kubuntu ppa
[05:11] <Kalidarn> i might have been imagining things
[05:12] <Kalidarn> if you have a phone or tablet
[05:12] <Kalidarn> when you plug it in do you see blank entries in the device manager
[05:12] <Kalidarn> or in dolphin
[05:12] <Kalidarn> i seem to with my nexus 5/nexus 7
[05:12] <Kalidarn> they all seem to point to camera:
[05:14] <Kalidarn> i imagine this bug occurs with any type of phone or tablet
[05:17] <jussi> Kalidarn: I think we talked about this the other day, no? 
[05:17] <jussi> did you try changing the desktop theme? 
[05:19] <Kalidarn> yes we did
[05:19] <Kalidarn> and it's not the desktop theme (using oxygen at the moment)
[05:19] <Kalidarn> but same issue with air
[05:19] <jussi> Kalidarn: I dont know then - it works here on both 14.04 and 13.10  w/backports
[05:19] <Kalidarn> the devices also appear blank in dolphin
[05:20] <jussi> Kalidarn: have you checked that you have it in the correct mode on the tablet/phone? 
[05:20] <jussi> ie. the storage one, not the camera one? 
[05:21] <Kalidarn> all i see in dmesg is
[05:21] <Kalidarn> [ 4884.740116] usb 1-4: new high-speed USB device number 13 using ehci-pci
[05:21] <Kalidarn> [ 4884.873358] usb 1-4: New USB device found, idVendor=18d1, idProduct=4ee2
[05:21] <Kalidarn> [ 4884.873363] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[05:21] <Kalidarn> [ 4884.873366] usb 1-4: Product: Nexus 5
[05:21] <Kalidarn> [ 4884.873368] usb 1-4: Manufacturer: LGE
[05:21] <Kalidarn> [ 4884.873371] usb 1-4: SerialNumber: xxxxxxxxxxxxxxxx
[05:21] <Kalidarn> oops :P
[05:22] <Kalidarn> all 3 seem to open to camera: 3
[05:22] <Kalidarn> camera:
[05:24] <Kalidarn> http://i.imgur.com/x1rTKFv.png
[05:24] <Kalidarn> looks really ugly and i'd like to try to find out what is causing it so it can be fixed for final release
[05:24] <Kalidarn> never happened with 3.10
[05:25] <Kalidarn> unfortunately i don't know what's causing it
[05:26] <jussi> Kalidarn: so did you check the device setting, as I mentioned?
[05:26] <Kalidarn> which one?
[05:26] <Kalidarn> i might have missed that
[05:26] <jussi> mtp/camera
[05:26] <valorie> interesting: my htc one phone has two devices reported: camera, and then the phone
[05:27] <Kalidarn> jussi: how do i check it?
[05:27] <valorie> but no blanks
[05:27] <Kalidarn> they both seem to open up to the same place
[05:28] <Kalidarn> the named one opens up to mtp: > Nexus 5
[05:28] <Kalidarn> the un named ones open up to Camera:
[05:29] <Kalidarn> and inside camera: there's a directory called "Google Inc (for LG Electronics/Samsung) Nexus 4/5/6/10 (MTP+ADB)
[05:29] <Kalidarn> with a store_000100001 directory in it
[05:29] <jussi> Kalidarn: when you connect the device, it should have a usb icon on the device pulldown. touch it, then choose mtp
[05:29] <Kalidarn> that seems to contain two text files about.txt and summary.txt
[05:30] <Kalidarn> jussi: i'm unsure what you mean
[05:31] <jussi> Kalidarn: plug in the usb. what appears in top corner of the nexus 5 screen
[05:31] <Kalidarn> oh
[05:31] <Kalidarn> yep
[05:31] <Kalidarn> hmm
[05:31] <Kalidarn> one of the hidden things went away when i disabled usb debugging ;)
[05:31] <jussi> pull down, click, make sure ownly mtp is selected
[05:32] <Kalidarn> ah yes MTP is only checked
[05:32] <Kalidarn> PTP is not
[05:32] <Kalidarn> after disabling usb debugging though it now only shows one blank entry
[05:33] <Kalidarn> the named one "Nexus 5" shows mtp: > Nexus 5 in dolphin
[05:33] <Kalidarn> and then a drive called "Internal Storage"
[05:33] <Kalidarn> that directs to /sdcard/
[05:34] <Kalidarn> the blank looking one (which there's only 1 of now) shows camera: and shows the "Google Inc (for LG Electronics/Samsung) Nexus 4/5/6/10 (MTP+ADB)" directory
[05:35] <jussi> Kalidarn: I suspect its a developer mode somethign
[05:36] <Kalidarn> possibly.
[05:36] <Kalidarn> i disabled developer mode completely and it still shows a blank one
[05:37]  * jussi goes back to work
[05:45] <jussi> apachelogger: http://sessellift.wordpress.com/2014/04/02/choose-your-own-experience-this-time-its-for-real/ - see, this is what I was talking about in Munich :D
[05:46] <jussi> mind, was funny that they first put it as april fools joke, then made a real one
[06:39] <lordievader> Good morning.
[06:57] <apachelogger> jussi: that'd be in voilation of our own UX practises
[06:57] <apachelogger> namely the "dont-get-in-the-way-of-the-user" one
[06:57] <jussi> :(
[08:01] <apachelogger> shadeslayer: it would appear to me that we need an explicit dep from whatever contains startkde to qdbus-qt4 | qdbus-qt5
[08:02] <apachelogger> or not
[08:02] <apachelogger> it's still fishy
[08:02] <jussi> who here was using kmail on 13.10 ?
[08:02] <apachelogger> for some reason I had qt5-default but not qdbus-qt5 installed
[08:56] <shadeslayer> apachelogger: nothing depends on qdbus-qt5
[08:57] <apachelogger> yeah
[08:57] <apachelogger> wouldn't have helped anyway if it's either or
[08:57] <apachelogger> you still can have the default config installed for qt5 but no qdbus-qt5
[08:58] <apachelogger> so it will qtchoose 5 but there is no binary there and then boom
[09:03] <ghostcube> o.O http://www.phoronix.com/scan.php?page=news_item&px=MTY1MzA   linus getting pissed eh?
[09:04] <apachelogger> high quality article, complete with typo and everything
[09:06] <ghostcube> dont be always so negativ apachelogger :D
[09:06] <apachelogger> but it is the truth
[09:07] <ghostcube> it is but the copy and paste parts are funny
[09:08] <apachelogger> *shrug*
[09:08] <apachelogger> always with the drama.
[09:09] <shadeslayer> hi
[09:09] <shadeslayer> morning
[09:09] <shadeslayer> forgot those two ^^ :P
[09:11] <ghostcube> :D
[09:37] <Mamarok> and mu0on still buggy, it again doesn't show a single package when filtering in the "All" part, and the xapian is up-to-date...
[09:37] <Mamarok> also, baloo-something is crashing repeatedly and now kde pim doesn't start anymore
[09:38] <Mamarok> and it doesn't update my notes, which luckily I completely backed up before re-trying Kontact...
[09:38] <Mamarok> but right now I can't access them because of kontact...
[09:38] <Mamarok> which sucks big time, I rely on these notes
[09:39] <vHanda> Mamarok: backtrace?
[09:39] <vHanda> for baloo
[09:40] <Mamarok> vHanda: sent by apport to launchpad, repeatedly the bug there already exists with multiple dupes
[09:40] <vHanda> could I have a link? It's probably been fixed, but just to be sure.
[09:40]  * apachelogger suspects that baloo is not watched by kubuntu-bugs
[09:40]  * apachelogger suspects that if that is the case someone will get pissed off
[09:41] <Mamarok> oh well, I have to digg that up apparently, can't you look in launchpad? Same effort
[09:41] <vHanda> nevermind.
[09:41] <apachelogger> https://bugs.launchpad.net/ubuntu/+source/baloo
[09:42] <vHanda> cool. Thanks. Fixed.
[09:44] <apachelogger> oh
[09:44] <apachelogger> there's more
[09:44] <apachelogger> marked private
[09:44] <apachelogger> most pointless feature in the world
[09:44] <Mamarok> why are thioes marked private? That is stupid
[09:44] <Mamarok> can't that be turned off by default for all our bugs
[09:45] <Mamarok> ?
[09:45] <apachelogger>  sudo baloo_file_extractor crashed with SIGSEGV in getint2() 
[09:45] <apachelogger> gee
[09:45] <Mamarok> yep, that bug
[09:45] <apachelogger> vHanda: bug 1301742
[09:45] <apachelogger> Mamarok: apport randomly marks bugs private or maybe it's the reporters
[09:45] <apachelogger> no clue
[09:45] <Mamarok> also I am happy to mention that I had my HD filled up again with baloo, such a change from nepomuk
[09:46] <Mamarok> very funny if you can't work anymore because your disk is full...
[09:46] <apachelogger> vHanda: bug 1300413
[09:46] <apachelogger> vHanda: bug 1298873
[09:46] <apachelogger> that's all
[09:46] <Mamarok> and sorry if I didn't report this before, I only decided yesterday to retry KDE PIM, based on good comments everywhere...
[09:47] <Mamarok> apparently still not my cup of tea...
[09:53]  * Mamarok just added a comment to bug 1301192
[09:54] <apachelogger> Riddell: ^ upstream is starting to get unhappy
[09:55] <Mamarok> starting is an euphemisms, to be honest, we already have a list of reports for that bug upstream
[09:55] <Mamarok> euphemism*
[09:56] <apachelogger> as long as we do unprepared library transitions a month before release the world is in order
[09:58] <Mamarok> :)
[09:58] <Mamarok> well, at least we have something we can point people at
[10:07] <vHanda> Mamarok: disk is full because of Baloo? Because of these crash reports?
[10:45] <Mamarok> vHanda: I am still trying to find out what filled up the disk exactly, but it all started with me starting KDE PIM
[10:46] <vHanda> let me know if it turns out to be Baloo. I've put in a lot of effort to make sure it is not like Nepomuk.
[10:47] <Mamarok> well, it has  position.DB file of 0,7 GB, a bit big, isn't that?
[10:48] <Mamarok> also, where can I choose what to index?
[10:49] <Mamarok> nvm, found it
[11:07] <BluesKaj> 'Morning all
[11:35] <Mamarok> vHanda: I found the culprit, it was a ~./.kde/share/apps/nepomuk/ folder with a total of 78 GB!
[11:35] <Mamarok> shoudln't there be no more nepomuk?
[11:39] <BluesKaj> Mamarok, just did an upgrade and saw some nepomuk lib files being upgraded, guess baloo is still using them.
[11:40] <Mamarok> well, just starting Kontact again after several months of no use, I ended up with over 70 GB filling up my hard disk in no time
[11:41] <BluesKaj> with email data?
[11:41] <Mamarok> I didn't even check if there was any data, I deleted the complete folder
[11:42] <Mamarok> so I could at least reuse my computer
[11:43] <Mamarok> and apparently that also fixed the muon isuse, now the search works again, so it was a space problem
[11:43] <BluesKaj> Mamarok, are you using akonadi and kmail as well ?
[11:44] <Mamarok> well, that is how everything started, I wanted to try kontact again, and ended up with having a full HD
[11:44] <jussi> kmail gets much faster when you switch the akonadi backend to postgres
[11:46]  * BluesKaj avoids akonadi and kmail
[11:50] <kdeuser56> jussi: which release are you on?
[11:50] <jussi> kdeuser56: 13.10 with ppa
[11:50] <kdeuser56> BluesKaj: no reason to do so
[11:50] <kdeuser56> jussi: does it work out of the box?
[11:50] <jussi> kdeuser56: does what work out of the box? 
[11:51] <kdeuser56> jussi: the postgres akonadi backend
[11:51] <jussi> kdeuser56: it appears to...
[11:51] <jussi> I clicked switch, then restart and kmail works, only faster
[11:51] <kdeuser56> jussi: are you using internal postgres server?
[11:52] <jussi> kdeuser56: yes
[11:52] <kdeuser56> jussi: and you simply switched the backend ... what happened to the data?
[12:10] <sgclark> Riddell: good morning, any tasks for me today?
[12:14] <Riddell> sgclark: well you could look at what's up with solid here http://qa.kubuntu.co.uk/kf5-status/build_status_4.98.0_trusty.html
[12:14] <kubotu> ::workspace-bugs:: [1299920] defaulting to qt5 does not work siunce QT_SELECT=qt4 is in the environment by default. @ https://bugs.launchpad.net/bugs/1299920 (by Søren Holm)
[12:14] <Riddell> sgclark: but it's very weird and I really have no idea
[12:14] <sgclark> Riddell: I will take a look
[12:15] <Riddell> "The following files are already published in Kubuntu Experimental:
[12:15] <Riddell> qtdeclarative5-kf5solid-5.0_4.98.0-0ubuntu1~ubuntu14.04~ppa5_amd64.deb"
[12:15] <Riddell> sgclark: it compiles fine but then fails to upload
[12:15] <Riddell> https://launchpadlibrarian.net/171639075/upload_5874921_log.txt
[12:15] <Riddell> is something nutty happening like it making that binary twice?
[12:18] <vHanda> BluesKaj: there is a nepomukbaloomigrator which runs once. It migrates all the tags, ratings and config files
[12:18] <vHanda> you can kill it and disable it if you don't care about the migration
[12:18] <sgclark> Riddell: indeed weird
[12:18] <vHanda> it's the only reason you need the nepomuk-core package
[12:21] <kdeuser56> vHanda: did you have a look into https://bugs.kde.org/show_bug.cgi?id=332686 ?
[12:23] <vHanda> kdeuser56: yes, but I cannot say if it has been fixed since I cannot reproduce it.
[12:23] <vHanda> I've pushed a number of changes, which should fix it.
[12:23] <BluesKaj> vHanda, i don't have baloo enabled, don't need it.
[12:23] <sgclark> Riddell: build log only shows one created, this is very odd
[12:23] <vHanda> ok
[12:27] <kdeuser56> vHanda: great!, thanks, I will see if it happens again
[12:28] <kdeuser56> vHanda: which release should the fixes be in?
[12:31] <sgclark> Riddell: changes only lists one... the only thing I can think to do is change ppa5 to ppa4, you went from ppa3 to ppa5
[12:59] <Riddell> sgclark: I got this reject e-mail
[12:59] <Riddell> "qtdeclarative5-kf5solid-5.0_4.98.0-0ubuntu1~ubuntu14.04~ppa5_i386.deb: Version older than that in the archive.                
[12:59] <Riddell> +4.98.0-0ubuntu1~ubuntu14.04~ppa5 <= 4.98.0-0ubuntu1~ubuntu14.04~ppa6                                                         "
[12:59] <Riddell> and for the ~ppa3 upload I got a reject e-mail saying ~ppa4 was in the archive
[12:59] <Riddell> I think launchpad is going nuts
[13:00] <shadeslayer_> wgrant_: ^
[13:01] <Riddell> oh, it's coming from kdeclarative
[13:01] <Riddell> wgrant_: it may be me who's going mad not launchpad
[13:01] <Riddell> that's what happens if you stay up until 04:30
[13:02] <sgclark> Riddell: figure it out?
[13:02] <Riddell> sgclark: I think I messed up kdeclarative which also made the solid package
[13:03] <Riddell> qtdeclarative5-kf5solid-5.0
[13:03] <sgclark> Riddell: ahhh
[13:03] <Riddell> should be qtdeclarative5-kf5declarative-5.0
[13:03] <Riddell> sgclark: could you check and fix that?