[02:16] <snele> dolphin 15.08 bug I was talking about few days ago
[02:16] <snele> i found the solution
[02:16] <snele> https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1490221
[02:16] <ubottu> Launchpad bug 1490221 in dolphin (Ubuntu) "Ship libkonq-common in order to fix dolphin 15.08 "create new" context menu" [Undecided,New]
[02:17] <snele> yofel: Riddell: ^
=== palasso_ is now known as palasso
[07:46] <lordievader> Good morning.
[09:06] <ovidiu-florin> ahoneybun: ping.. r pong?
[09:06] <ovidiu-florin> what's VDG aproved?
[09:06] <ovidiu-florin> what slides do you want me to help you with?
[11:02] <BluesKaj> Hey folks
[13:24] <doko> is there anybody who can read https://notes.kde.org/p/kubuntu-kdepim-15.08-transition and could paste that?
[14:12] <ahoneybun> ovidiu-florin: the website was VDG approved at akademy lol
[14:12] <ahoneybun> also Linux slides
[16:17] <shadeslayer> willy xD
[16:17] <shadeslayer> doko: sure, moment
[16:18] <shadeslayer> doko: http://paste.ubuntu.com/12231491/
[16:50] <TJ_on_Wily> Testing 15.10; session start-up seems to take an abnormally long time but as xsession-errors doesn't contain timestamps I'm not sure how to debug/report it
[16:53] <BluesKaj> heh, i can't seem to get rid of ramdisk in 15.10 even after 2 clean installs 
[16:53] <TJ_on_Wily> ramdisk? what ramdisk?
[16:56] <BluesKaj> dunno, it was something I thought I'd try afew weeks ago 
[16:56] <TJ_on_Wily> well if you do a clean install a ramdisk isn't going to remain; it requires a specific configuration
[16:57] <BluesKaj> it doesn't exist on my 14.04
[16:57] <TJ_on_Wily> Where - or how - exactly do you see this ramdisk?
[16:58] <BluesKaj> then i must have that specific config , sudo fdisk -l , lists 16 of them from 0-15
[16:59] <ejat> http://paste.ubuntu.com/12231849/ <-- 
[17:00] <ejat> yofel & soee: r u there?
[17:00] <TJ_on_Wily> BluesKaj, haha, yeah I see them 
[17:01] <TJ_on_Wily> Kernel configuration:
[17:01] <TJ_on_Wily> CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=1 CONFIG_BLK_DEV_RAM_SIZE=65536 CONFIG_BLK_DEV_RAM_DAX=y
[17:01] <TJ_on_Wily> I'll check with the kernel team on why that has been set
[17:02] <BluesKaj> so you have them too TJ_on_Wily, was it you who suggested that over at ##linux ?
[17:03] <TJ_on_Wily> Doubt it; First time I've paid attention to it
[17:04] <BluesKaj> Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
[17:05] <BluesKaj> I don't see anything like the line you posted , TJ_on_Wily
[17:05] <TJ_on_Wily> They exist in the Trusty kernel too: 3.13.0-62-generic has CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=65536
[17:06] <TJ_on_Wily> BluesKaj, That line comes from grepping the kernel config in /boot/
[17:06] <TJ_on_Wily> I don't think the issue is the existence of the RAMdisks; I think it is that the newer fdisk is listing them
[17:07] <BluesKaj> the list in trusty doesn't exist here
[17:08] <BluesKaj> I have 14.04 as well, dual boot
[17:09] <TJ_on_Wily> BluesKaj, the RAMdisks are still there; just fdisk -l doesn't show them
[17:10] <BluesKaj> ok , because they aren't configured I suppose
[17:11] <TJ_on_Wily> They are, that's my point. On trusty do "cat /proc/partitions" and you'll see them. That's how fdisk gets the list, but it looks like in the older version of the libmount library that fdisk uses it filters out RAM disks
[18:29] <clivejo> does KDE have any kind of SIP VOIP services built in?
[19:33] <BluesKaj> does this new audio volume icon in the system tray replace kmix in Wily?
[19:35] <clivejo> is it not just a wrapper for kmix?
[20:31] <TJ_on_Wily> Testing 15.10; session start-up seems to take an abnormally long time but as xsession-errors doesn't contain timestamps I'm not sure how to debug/report it, anyone know a way to analyse the session start-up. LXDE doesn't have the problem.
[20:32] <TJ_on_Wily> Also, is abiword supposed to be started automatically at log-in? Not been able to figure out where that is being started from
[20:34] <clivejo> TJ_on_Wily: did you leave it open when you ended the previous session?
[20:35] <TJ_on_Wily> clivejo, Fresh install of Wily, first log-in it loaded with an empty document, and continues to do so. If I uses an LXDE session it doesn't start, so it is something to do with Kubuntu
[20:35] <clivejo> very strange!
[20:36] <TJ_on_Wily> that's what I thought... usually I'd discover what is launching it within a few minutes, but I've not found it yet after several hours looking, on and off
[20:38] <TJ_on_Wily> I swapped out the HDD for an empty one so there's nothing left over from previous installs, which makes it stranger
[20:38] <clivejo> is abiword installed by default on a clean install?
[20:42] <TJ_on_Wily> This is the weird bit... it's a dependency of lubuntu-desktop - but doesn't autostart with that :s
[20:44] <TJ_on_Wily> The only clue I could find is a cached log entry: "/home/tj/.cache/lxsession-default-apps/run.log:81:** Message: combobox.vala:443: Defaut = abiword" - I wonder if the mis-spelt 'Defaut' is part of the issue
[20:56] <TJ_on_Wily> Hmmm... is a changelog or welcome document of some kind supposed to be displayed after a fresh log-in ... I wonder if it is empty/missing but abiword is the registered handler for it