[00:34] <Riddell> valorie: was the problem you had with next and next-backports just the kf5 update problem?
[01:32] <sgclark> Riddell: yeah sorry still having issues with my mail server and couldn't respond. I have to focus on my web server atm sorry :(
[02:11] <VolUTFan> I found a menu bug in vivid with KDE Partition Manager trying to open.  Running cmd ubuntu-bug partitionmanager doesn't give me an option to add notes.  When you open the app from the menu, gives you an error, from terminal no problems.
[02:12] <VolUTFan> im not sure there is an actual problem with the application, but rather with the way it is being called from the kicker menu.  How can I effectivelly report this
[03:08] <ScottK> VolUTFan: report the bug using ubuntu-bug and then after the initial report is done, you can add the information. Once you've done so, feel free to ping me.
[03:08] <VolUTFan> so far in an hour I have found 5 bugs
[03:08] <VolUTFan> will do
[03:11] <VolUTFan> Do I need to throw my hardware profile in the notes?  or with the ubuntu-bug app grab that
[03:45] <VolUTFan> Scott, I logged the bugs the best I can.
[05:09] <mitya57> ScottK: No problem, I will fix & reupload today (but it will be 5.4.1).
[05:59] <valorie> Riddell: yes, that day I did a regular update/upgrade
[06:04] <valorie> soee: I'm using konvi in Vivid
[06:04] <valorie> right now, in fact
[06:11] <valorie> and I've never seen a spike in CPU use
[07:04] <ejat> hi .. i just upgrade to vivid .. 
[07:04] <ejat> after login to plasma .. 
[07:04] <ejat> i dont have the application bar/frame 
[07:05] <ejat> anything that i can do to reset ? or etc ? 
[07:07] <valorie> support is in #ubuntu+1 ejat
[07:07] <valorie> or #plasma
[07:07] <ejat> okie thanks valorie 
[07:23] <ejat> i cant see kwin_x11 package
[07:24] <ejat> owh my bad .. kwin :) 
[07:34] <valorie> that is bad
[08:05] <lordievader> Good morning.
[10:21] <sitter_> Riddell: ping
[10:43] <Riddell> hi sitter 
[10:44] <sitter> Riddell: yo. libkdegames and libkmahjongg in apps 15.04 will be kf5 based we will still have dependees on kdelibs4 though ... so question is should the new source be renamed or the old?
[10:44] <sitter> i.e. libkdegames-kf5 or libkdegames-kdelibs4
[10:48] <sitter> also should I ditch the epoch? there will be no package overlap
[10:48] <Riddell> sitter: good question but a gooder question first might be what do we want to do with 15.04
[10:48] <Riddell> I assume it's too late for Kubuntu 15.04
[10:48] <Riddell> so it'll be for kci and kubuntu 15.10?
[10:49] <sitter> yeah
[10:49] <sitter> well, kubuntu 15.10 and backports PPA
[10:50] <Riddell> good point
[10:50] <sitter> kci + kubuntu 15.10 + backports PPA xD
[10:51] <Riddell> how about following what happened with konsole4 and kate4 and have a libkdegames4 ?
[10:51] <sitter> fine by me
[10:51] <valorie> first tragedy in vivid: no kpatience!
[10:51] <sitter> Riddell: what to do with kdegames-card-data ... kdegames-card-data-kf5?
[10:52] <valorie> so i had to work instead of wasting time
[10:52] <sitter> fun story: that data package had a more reasonable albeit unreadable name earlier ;)
[10:53] <Riddell> sitter: the same pattern would be to treat the old one as the recovered one and have kdegames-card-data4
[10:53] <Riddell> and the new one as the new norm and have kdegames-card-data
[10:53] <sitter> also on a related note ... the naming scheme qml-module-foo is going to cause major headaches when qt6 comes along
[10:54] <Riddell> qml is a naming headache in itself
[10:54] <sitter> Riddell: for kdegames renaming the old data means a lot of adjustment though
[10:54] <sitter> also it means I need to CI the old libkdegames which is the bigger tragedy here xD
[10:55] <Riddell> ok do whatever is easiest then :)
[10:55] <sitter> pft :P
[10:57] <Riddell> but it's nice to avoid having to rename sources compared to upstream is my thinking and we'll have the new kf5 sources around for more than the old kdelibs4
[11:01] <sitter> Riddell: I entirely agree as far as sources are concerned. for binaries that provide shared stuff it's generally meh though as with kdegames-card-data. those should probably grow a version
[11:02] <sitter> otherwise we have to do the same crap for kf6, also that's the problem with the qml-module stuff
[11:05] <sitter> oh
[11:06] <sitter> mitya57: please add the kde-buildsystem group to the lconvert review
[11:08] <sitter> and sorry, I didn't realize that group wasn't on the review previously
[11:09] <mitya57> Ok.
[11:12] <sitter> Riddell: then again about the data package ... the only reason the new version isn't a drop-in replacement for the old data package is because the paths are different so that might very well not be a problem for kf6
[11:12]  * sitter very torn now
[11:20] <sitter> Riddell: http://anonscm.debian.org/cgit/pkg-kde/applications/libkdegames.git/commit/?h=kubuntu_unstable&id=d494c1c2cb4a90218f6a58b740874a607a5fb8bb
[11:29] <Riddell> sitter: looks good
[11:49] <Riddell> hoo rah, calligra went in
[11:49] <Riddell> I don't know why but every time I touch that package it takes 10 times longer than it should
[11:56] <sgclark> morning
[11:57] <lordievader> o/
[12:00] <sitter> actually
[12:01] <sitter> Riddell: maybe we should just call it libkf5kdegames-data? kmahjongg has the exact same situation and by simply using the library name we get the versioning bit for free anyway
[12:10] <Riddell> sitter: good idea
[12:10] <Riddell> hi sgclark!
[12:11]  * Riddell spots bug 1427654
[12:12] <sitter> zomgzomg
[12:12] <sitter> Riddell: btw do you ahve any updates on bluez?
[12:12] <sitter> I feel like I should go on a rant
[12:13] <Riddell> sitter: nope, still waiting on whatever still needs ported on the unity side, rant at didrocks if you think it'll help
[12:14] <Riddell> or work out how to make it co-installable but that probably lots of work
[12:14] <sitter> impossibru
[12:14] <sitter> stack needs pulseaudio built against bluez5
[12:14] <Riddell> mm
[12:14] <sitter> then again a bluetooth without audio support is better than no bluetooth >.<
[12:35] <soee> good moring
[12:38]  * Riddell publishes http://www.kubuntu.org/news/calligra-2.9
[12:38] <soee> Riddell: what about kdetelepathy ?
[12:39] <sitter> soee: I think you saw load problems in konversation? ... if so konvi dev says go to interface -> chat window in the config dialog and disable the scroll bar ... see if that helps
[12:39] <sitter> also pass it along in case you know anyone else who has seen the problem
[12:40] <sitter> oh and report back to me or #konversation
[12:41] <soee> sitter: let me check, 
[12:46] <soee> sitter: ekm, that wasn't it. my problem was that konversation icon was always visible in tsk manager, now i right click on the icon and picked to remove that launcher and it is gone 
[12:47] <soee> and i have no idea why this one icon worked liek some separate launcher
[12:49] <Sho_> soee: hi - sitter tells me you have various problems with konvi5?
[12:50] <sitter> Sho_: http://paste.ubuntu.com/10514803/ backlog for your convenience
[12:50] <Sho_> thanks~
[12:51] <soee> Sho_: Kai has more serious issue where konv starts to use 100% CPU i think
[12:51] <Sho_> soee: the "why this one icon worked differently" is probably because you're (understandably) confused between the two types of launchers you can have on a plasma panel: task manager launchers (right-click task -> show icon when program is not running) and icons on the panel (which are indepentent of the task manager(
[12:51] <soee> BluesKaj: ^ ami right ?
[12:52] <Sho_> soee: as for why the launcher would go: the .desktop file got renamed between the kde 4 and kf5 versions to comply with a new desktop file naming pattern in kde
[12:52] <BluesKaj> Hiyas all
[12:53] <soee> Sho_: ok, tanks. One more thing the bug with moving char log directly to home folder is fixed ?
[12:53] <soee> *chat logs
[12:54] <Sho_> soee: that was a kubuntu bug
[12:54] <ScottK> We're in favor of systemd for this cycle, right?
[12:54] <sitter> ScottK: yes
[12:54] <Sho_> soee: they overrided our default logs location and forgot to keep the override for the kf5 version
[12:54] <Sho_> soee: so sitter gotta respond to that one :)
[12:54] <ScottK> OK.  FFe to switch has been submitted.
[12:54] <soee> Sho_: ok, thanks once again :)
[12:55] <sitter> Sho_: have you given any thought to changing the storage path upstream btw?
[12:56] <sitter> seems to me that we'd only need a kconf_update script that moves $HOME/logs? possibly symlink to new location
[12:56] <sitter> ScottK: <3
[12:58] <BluesKaj> soee, yes, just checked, one core of my 2 core cpu remains maxed on certain chats in konversation like #kubuntu. #kubuntu-devel and ##linux
[12:58] <soee> Sho_: ^
[12:58] <BluesKaj> the others are at a normal 5-10% or so 
[13:00] <Sho_> sitter: in the past you did it with a custom konversationrc in the profile
[13:01] <Sho_> BluesKaj: please try switching off the scrollbar in Interface -> Chat Window and see if it helps
[13:01] <Sho_> sitter: If we had changed the storage path upstream it'd have broken too btw since $KDEHOME fell out of use now
[13:01] <Sho_> sitter: So ironically our $HOME/logs was more stable
[13:02] <sitter> you could always have used $HOME/.konversation though
[13:02] <sitter> if the directory was called konversation-logs I'd probably be less annoyed by it already (though putting random things in the visible home is meh in general)
[13:02] <Sho_> sitter: not the one you guys picked either tho
[13:03] <sitter> Sho_: yeah, I am not debating the sillyness of our setting override there
[13:04] <BluesKaj> Sho_, no difference
[13:04] <Sho_> BluesKaj: do you know how to use perf or gdb?
[13:04] <Sho_> sitter: before we can change it we need to write some migration code
[13:05] <BluesKaj> Sho_, they were mentioned before, but I'm not familiar with perf or gdb 
[13:05] <sitter> fwiw, you could try to enable the kwin redraw effect to see whether there's obvious business in konversation
[13:05] <Sho_> good idea, too
[13:06] <Sho_> could you give that a shot BluesKaj?
[13:06] <sitter> Sho_: regarding the migration code, do you think it would be more than a simple kconf_update that moves the directory to the new location?
[13:06] <BluesKaj> Sho_, so what am I looking at ?
[13:08] <sitter> alt-space -> effects -> search for paint and enable it
[13:08] <sitter> that should make your desktop go all rainbowy
[13:08] <sitter> make sure you don't have any videos running as that will rainbow way too much
[13:08] <Sho_> sitter: kconf_update is extremely unreliable, i don't think it'd be ok in the wild
[13:08] <sitter> then go into an affected channel and check if the konversation window or parts of it blink excessively
[13:09] <sitter> Sho_: :O that seems like an odd thing to say considering everyone is using it in production releases ^^
[13:09] <Sho_> sitter: yes, and it breaks shit for users all the time
[13:09] <Sho_> sitter: the kded module finds and runs new kconf_update scripts at runtime, i.e. when konvi is running while the user installs the new version it'd move the logs and then you'd have unmerged log files in two locations
[13:10] <sitter> Sho_: simply function called from main() instead perhaps?
[13:10] <Sho_> sitter: this is also why quitting an app after updating it can undo settings changes because the app flushes out their config on quit and overwrites anything kconf_update did to the same keys, and few devs think to switch key names because they don't know the problem
[13:10] <sitter> *simple
[13:10] <Sho_> sitter: thanks to kconf_update kde effectively doesn't support updates at runtime
[13:10]  * sitter did not know kded was involved
[13:11] <Sho_> sitter: that's what runs kconf_update scripts
[13:11] <sitter> so yeah, to avoid runtime problems we could simply migrate in main()... as I was saying, ideally the migration code would be nothing more than a Dir.move
[13:11] <Sho_> sitter: you might think it'd be done in-process by the app, but that would be sane or sth, so it's not how it was done
[13:12] <sitter> ^^
[13:13] <Sho_> sitter: yeah, we'd need to do it like this: add a new kconfigxt key for the new log dir, at startup find out whether the current log dir was ever changed from the kconfigxt default for the old key, if not assume the user never changed their log dir and is eligible for migration, block chatting until that migration has been attempted, throw up an info dialog with progress for the move, and handle write errors
[13:13] <Sho_> something like that
[13:15] <sitter> Sho_: would we need to check the config at all though? if Dir.exist?('~/logs') ...
[13:15] <BluesKaj> Sho_, so what's to be done?
[13:15] <sitter> that of course has the beautiy flaw of potentially moving logs dirs other than konversation's :P
[13:15] <sitter> then again checking configs isn't necessarily helping that
[13:16] <Sho_> sitter: we need to check the config to find out if the user ever set a custom log path, and if they have, don't touch it
[13:16] <sitter> could be that the user starts konversation for the first time and thus has no custom dir set, but perhaps already has a logs/ dir for some other piece of software he's using
[13:16] <Sho_> sitter: there's no point to move dirs if we don't know they're in use, either
[13:16] <sitter> Sho_: you mean if they set it explicitly to ~/logs?
[13:16] <Sho_> BluesKaj: enable the repaint effect and see if you see konvi repainting even if there's nothing new to show
[13:17] <Sho_> sitter: no, if they set it explicitly to somewhere other than the default
[13:18] <Sho_> sitter: the above approach also has the advantage that it would catch your .kde path too and migrate from it as well
[13:18] <Sho_> sitter: since it would attempt to migrate away from any unchanged system default
[13:19] <Riddell> soee: what do you want to hear about kde telepathy?
[13:19] <sitter> I think I need to read the backlog again, I am not seeing the advantage
[13:20] <Sho_> sitter: we currently have konvis in the wild that use two log dirs that we consider undesirable for different reasons ($HOME/logs because whatever, .kde/... set by kubuntu 'cause outdated), which are specified in the .kcfg shipped with konvi and your system-level konversationrc override, respectively
[13:21] <sitter> Sho_: ah ah, I think I get it. that's still only marginally more complicated than if Dir.exist ... though, not exactly rocket science that one. I'll try to get you something to review rather than twiddle our old setting override back in place
[13:21] <Sho_> sitter: so the idea is that konvi figures out whether the user has ever manually changed the log path or not, and if not, proposes + attempts to move the logs to ~/.koversation-logs or whatever
[13:22] <Sho_> sitter: well, it needs user interaction (dialog that asks, kio move progress) and error handling (new location not writable, etc.)
[13:23] <Sho_> and it should pop up after the main window does, but before any connections are made
[13:24] <sitter> Sho_: why would it present a dialog?
[13:25] <BluesKaj> Sho_, there's a constant repaint every half second or so 
[13:25] <sitter> there's no dialog asking the user whether the user wants to use ~/logs, presenting one when changing the default seems rather inconsistent 
[13:26] <BluesKaj> Sho_, on everything
[13:27] <Sho_> sitter: because moving logs from the location the user is already used to without informing them is pretty weird
[13:27] <sitter> BluesKaj: that's probably from the input field cursor blinking
[13:27] <sitter> BluesKaj: try clicking on the log and check if it still repaints
[13:27] <Sho_> the input cursor blinking doesn't repaint the entire window on my konvi though
[13:28] <Sho_> only the cursor caret
[13:28] <Sho_> a half-second interval is pretty slow to be the cpu usage problem though
[13:29] <BluesKaj> everything repaints here , dunno what you mean by the cursor blinking , I don't see that here ...it's the whole desktop
[13:29] <sitter> Sho_: I kind of agree. But in the large scheme of things it kinda drowns in the fact that we moved to completely new directories for configs and whatnot without even informing the user and most apps not actually carying their data out of $KDEHOME as part of the process
[13:29] <sitter> Sho_: at any rate. rather than annoy the user with a dialog they might not understand I'd simply move and symlink tbh
[13:29] <Sho_> sitter: we completely fucked up the kde apps release if you asked me (and still haven't unfucked it)
[13:29] <BluesKaj> sitter, clicking on which log?
[13:29] <sitter> that way things don't get "lost" to the user
[13:30] <Sho_> sitter: i assume you saw https://mail.kde.org/pipermail/release-team/2015-January/008292.html
[13:30] <sitter> yes
[13:31] <sitter> BluesKaj: the backlog
[13:34] <BluesKaj> sitter , nothing
[13:34] <sitter> BluesKaj: it still keeps a core busy though, right?
[13:35] <BluesKaj> sitter, hang on
[13:35] <sitter> shadeslayer, Riddell: it woudl be very lovely if you could comment on the phonon review I posted yesterday
[13:35] <sitter> and maybe poke sune into doing that as well
[13:35] <BluesKaj> sitter, the core is constant at 100% in this chat, no matter what 
[13:36] <Riddell> sitter: where is?
[13:36] <Riddell> https://git.reviewboard.kde.org/r/122777/ ?
[13:36] <sitter> BluesKaj, Sho_: right, so the problem isn't repaints
[13:36] <sitter> Riddell: yes
[13:36] <BluesKaj> if I go to offtopic it drops to 3%
[13:37] <sitter> fixes debian being annoyed about the fact that you can't have libphonon-dev without libphononexperimental-dev...
[13:38] <Sho_> BluesKaj: please install perf, cause the cpu usage and then run perf top -p $(pidof konversation)
[13:38] <Sho_> BluesKaj: then let it run for like 30 seconds and pastebin the first page or so of output
[13:38] <sitter> package linux-tools-generic if I am not mistaken
[13:43] <Riddell> sitter: seems sane, my cmake foo isn't strong enough to be able to point out specific issues with it, I can build it and see if it does the right thing if you think that would help
[13:44] <sitter> whatever makes you give it a shipit ;)
[13:47] <Riddell> sitter: what changes would need to be done to the cmake files of a project using phonon
[13:49] <sitter> none
[13:49] <Riddell> sitter: even one that used phonon experimental?
[13:49] <sitter> cmake files that use phononexperimental technically also don't need changes as long as the code was correct to begin with
[13:50] <sitter> nothing should break by the way the change was made. it really is just a half-assed optionalism to make debian happy
[13:53] <sitter> a build that previously failed without experimental becuase it requires experimental will continue to fail. a build that previously succeeeded because it didn't use experimental anyway will continue to succeed. a build that previously succeeded and is using experimental will continue to do so *as long as the experimental dev package and lib are installed* (which was a prequesite to it suceeding anyway)
[13:54] <BluesKaj> Sho_, there's no perf available for the linux 3.19 kerenel , apt suggests installing linux-tools-3.19.0-7-generic but the repos connection failed, it stalled at the header for a period of time then went back to the prompt 
[13:54]  * sitter done packaging the apps15.04 repos he is aware of >.<
[13:54] <sitter> BluesKaj: [14:38] <sitter> package linux-tools-generic if I am not mistaken
[13:55] <sitter> the unversioned packages will pull in the latest version ensuring you have a matching lineup of kernel and kernel tools
[13:56] <BluesKaj> sitter yes that command fails, apt suggests to install the linux-tools-3.19.0-7-generic pkg , but that's what fails
[13:56] <BluesKaj> as well
[13:56] <sitter> use archive.ubuntu.com as repo
[13:56] <BluesKaj> I'll try 
[14:05] <BluesKaj> sitter, getting a hash sum mismatch with http://archive.ubuntu.com/ubuntu/dists/vivid/universe/source/Sources , both 64 and 32 bit 
[14:07] <sitter> try again in 5 minutes
[14:07] <sitter> or simply disable sources :P
[14:07] <BluesKaj> http://archive.ubuntu.com/ubuntu/dists/vivid/universe/source/Sources 
[14:35] <BluesKaj> Sho_,  I have perf top -p $(pidof konversation) running in th eterminal , but how to freeze it to save the text ?
[14:36] <BluesKaj> print to perf.hist.N in the help dialog doesn't do anything, no such file
[14:39] <Sho_> BluesKaj: I'd say just select quickly and middle-click in kate to paste
[14:42] <BluesKaj> Sho_, I managed to save some to a textfile http://pastebin.com/psBP8TX1
[14:47] <Riddell> hi manchicken 
[14:47] <Riddell> did you ever get a chance to look at muon manchicken?
[14:48] <BluesKaj> one can use the scrollback-save as option to a text file 
[14:48] <BluesKaj> in perf
[14:48] <sitter> oxygen, I blame oxygen
[14:48] <sitter> BluesKaj: which window decoration do you use?
[14:50] <sitter> Sho_: I feel likeI should mention now that changing the widget style crashes konvi without drkonqi coming up :|
[14:51] <Sho_> sitter: reproducably? if so: gdb
[14:51] <sitter> wip
[14:51] <soee> would it be possible to show custom backgraund image for sddm in the theme details image http://wstaw.org/m/2015/03/03/worksace12.png ?
[14:52] <soee> or maybe also on the items list 
[14:52] <Sho_> BluesKaj: lots of Oxygen widget style stuff in the perf output ... interesting, because I use Breeze and maybe that explains why I don't see CPU usage
[14:52] <BluesKaj> sitter, using breeze atm
[14:53] <soee> Riddell: the current version is not using kf5 or am i wrong (@ kde-telepathy)
[14:54] <Riddell> soee: no it's not and we won't get a release in time for kubuntu 15.04
[14:54] <Riddell> but maybe we should ask for a release of the applet or something
[14:54] <sitter> hm, ubuntu archive doesn't like me today
[14:54] <sitter> Sho_: reproducible http://paste.ubuntu.com/10515900/
[14:54]  * soee hugs sitter
[14:55] <sitter> can't get symbols right now, though from the looks of it symbols wouldn't help much anyway
[14:55] <Sho_> sitter: not a konvi fuckup at least by the looks of it
[14:55] <soee> Riddell: and the applet can get into Vivid ?
[14:55] <sitter> yeah it must have to do with something konvi does though
[14:55] <sitter> no other app blows up
[14:55] <BluesKaj> shadeslayer, switched the widget style to breeze anf that  crashed konversation , but didn't change the cpu load , still the same
[14:55] <sitter> Sho_: it's also interesting that drkonqi doesn't come up
[14:55] <sitter> all very peculiar
[14:56] <BluesKaj> oops Sho_ ^
[14:56] <sitter> I think I can give up on debugignt this today I am having 56k speeds to archive.ubuntu xD
[14:57] <BluesKaj> sitter, same here ...very slow 
[14:58] <soee> someone know if ther eis any proggress with https://bugreports.qt.io/browse/QTBUG-40207 ?
[18:00] <beluga_> Plasma 5.2 & LibreOffice testers wanted: https://bugs.documentfoundation.org/show_bug.cgi?id=89537 Color picker and highlight dropdown button does not work very well on KDE Plasma 5
[18:04] <KDDA> are there any guides about packaging for Kubuntu?
[18:11] <soee> KDE Ships KDE Applications 14.12.3
[21:10] <mparillo> KDDA: When I was trying (and failing) to package rekonq, here are my notes. http://pastebin.ubuntu.com/10519556/ During the European day time, you will find lots of people willing to help you learn packaging.
[21:11] <KDDA> mparillo: thanks
[21:14] <mparillo> KDDA: I would be happy to create a guide, but I never got it to work (mostly because of my keys), and I think publishing and improving it would be better than Riddell hand-holding newbies like me.
[21:22] <yofel> KDDA: in general, there's the ubuntu packaging guide (but ignore the bzr specific UDD stuff), and the debian new maintainers guide (which is a bit old and doesn't mention a VCS, but still a nice intro)
[21:22] <yofel> other than that, learning by doing is usually the way
[21:25] <KDDA> not sure where to start!
[21:26] <KDDA> Id like to see tilemill packaged for vivid
[21:27] <alket> fix dolphin pls
[21:28] <KDDA> dolphin is working ok for me
[21:28] <KDDA> whats your problem with it?
[21:28] <yofel> alket: like I said, we would first need a hint to what's wrong...
[21:29] <alket> how can I help
[21:29] <alket> I can crash dolphin easy hehe
[21:29] <KDDA> how do you crash it?
[21:30] <alket> I can give you KRDC access if you want
[21:30] <KDDA> run it via a terminal and get the error messages
[21:31] <alket> KDDA: open a file with kate, work on in let say , 10 min, then go to dolphin and click on side panel
[21:31] <alket> also Konversation saves logso n home directories
[21:31] <alket> ~/logs
[21:32] <yofel> which side panel? Information?
[21:32] <KDDA> I open files in Kate all the time :/
[21:32] <yofel> alket: sitter and Sho were talking about fixing the log dir today
[21:35] <alket> thank yofel
[21:35] <alket> as soon as dolphin crashes (can't get it to crash right now)
[21:35] <alket> ill send report
[21:36] <yofel> thanks
[21:37] <alket> also wx looks unusable
[21:37] <alket> try filezilla
[21:38] <yofel> WTH
[21:38] <alket> ?
[21:38] <yofel> well, I see what you mean o.O
[21:39] <alket> backspace and some keys don't work
[21:39] <alket> also is there a channel support for kftpgrabber
[21:40] <yofel> backspace works here, but I do remember it not working once a while ago
[21:40] <yofel> for me the UI just looks... misligned
[21:41] <alket> I have wxwidgets 3.0.2
[21:41] <yofel> same
[21:41] <alket> and Kernel 3.8.x
[21:42] <alket> 3.9 gives me black screen
[21:42] <yofel> hm.. what's my gtk3 theme...
[21:42] <alket> 3.18
[21:42] <yofel> Orion
[21:44] <KDDA> black screen where?
[21:44] <KDDA> can you log in?
[21:45] <alket> KDDA: no, but I use xorg, so i dont blame it, but wanted to note maybe that could be the cause of wxwidget missbehaviour
[21:45] <alket> xorg = xorg edgers PPA
[21:46] <KDDA> when I was tryig to upgrade I kept getting a black screen and white mouse pointer, nothing else
[21:46] <KDDA> fresh install worked, but when I copied my home folder over it died again
[21:50] <yofel> alket: plain vivid with nvidia here and filezilla looks like this: https://yofel.dyndns.org/owncloud/index.php/s/iSgCrHe9PGnNlT6
[21:50] <alket> your SSL is expired
[21:51] <alket> lol, but your theme looks good though
[21:51] <yofel> is it? It's self signed..
[21:52] <KDDA> I cant access it :/
[21:52] <alket> yes me too, but it needs to add exception
[21:52] <KDDA> oh wait, its just slow
[21:53] <alket> its from home connection i think
[21:53] <yofel> yup ^^
[21:54] <KDDA> see it now
[21:54] <KDDA> how do you get it to do that?
[21:55] <yofel> to do what?
[21:55] <alket> you need to config router
[21:55] <alket> I have public ip though, but slow upload
[21:55] <KDDA> the swadow
[21:56] <yofel> I'm confused, do you mean the tooltip?
[21:57]  * alket common dolphin, crash
[21:57] <KDDA> the screen shot
[21:57] <KDDA> how do you make filezilla do it
[21:58] <yofel> not filezilla, that was ksnapshot (using rectangular region with a 1s delay to catch the tooltip)
[21:58] <KDDA> oh, misunderstood you
[21:58] <KDDA> I been using filezilla a lot today and didnt see anything like that!
[21:59] <yofel> if you hover over the "Host:" input field with your mouse it'll show a popup telling you what's valid in there
[21:59] <yofel> for some reason Orion renders that with white text -.-
[22:00] <yofel> s/popup/tooltip/
[22:00] <kubotu> yofel: You did something wrong... Try s/you/me/ or tell me "help sed"
[22:08] <alket> konversation also doesn't order nick list based on ranks, but just ASC
[23:05] <alket> yofel: dolphin doesn't save the "Add to places"
[23:20] <alket> yofel: dolphin crash: https://paste.kde.org/pzwyxxjws
[23:21] <KDDA> looks like issue with X
[23:24] <valorie> odd error message today in updates to Vivid beta: https://paste.kde.org/pjrqqsczr
[23:24] <valorie> they were successful, but Setting up apparmor failed
[23:39] <valorie> dunno whether that is worth a bug report however