[10:47] <melodie> hi
[10:48] <melodie> I am install Wily as of yesterday in virtualbox, on a new vdi file. The installer was unable to provide the "continue" button until I added a table partition from within Gparted
[11:07] <phillw> melodie: never came across that issue... which version of wily were you using?
[11:07] <melodie> the one whose link you gave me a pair of days ago
[11:08] <phillw> I'll go and install VBox :: coughs ::
[11:08] <melodie> I am trying to narrow your double icons bug but atm I haven't found where the issue lies
[11:09] <phillw> I'm jjust installing VBox and will then try it. The issue has not been reported by anyone, so I am a bit puzzled.
[11:09] <melodie> yes, it's astonishing
[11:10] <melodie> or maybe it's a unique bug that popped out from nowhere, who knows?
[11:10] <phillw> i don't think we're ALL using KVM, but it is a possibility.
[11:12] <phillw> are you using 32 or 64 bit install?
[11:14] <melodie> i386
[11:17] <melodie> phillw I found where the bug is for the 'â' applet I think
[11:18] <melodie> this is the fcitx program well unfortunately, the bug seems to be in the program itself
[11:18] <melodie> so the program needs debugging
[11:19] <phillw> grabbing  lubuntu-15.10-beta1-desktop-i386.iso from http://cdimage.ubuntu.com/lubuntu/releases/15.10/beta-1/
[11:21] <melodie> not sure yet about what I just said
[11:21] <melodie> I have one more test in mind
[11:30] <melodie> when starting fcitx from console it complains there are more xim daemons started, suggesting from ibus
[11:30] <melodie> for nm-applet I don't know yet
[11:42] <melodie> phillw this double-icons bug could be the top visible clue to a larger issue
[11:42] <melodie> -_-
[11:42] <phillw> hmmm...
[11:53] <phillw> bbs ... reboot needed.
[11:59] <phillw> back :)
[12:03] <melodie> whatever I do, fcitx is started magically
[12:06] <phillw> hmmm
[12:06] <phillw> ps -ef | fcitx
[12:06] <phillw> The program 'fcitx' is currently not installed. You can install it by typing:
[12:06] <phillw> sudo apt-get install fcitx-bin
[12:07] <melodie> wrong
[12:07] <melodie> this is your â applet
[12:08] <melodie> rather try:
[12:08] <melodie> ps ax | grep fcitx
[12:09] <phillw> on my production machine, I do not have the  â applet at all, but do have 2 nm-applets and 2 skype applets
[12:09] <melodie> phillw there are double of mostly everything in there
[12:09] <phillw> ps ax | grep fcitx
[12:09] <phillw>  2921 pts/0    S+     0:00 grep --color=auto fcitx
[12:10] <melodie> just install htop, start it in console and
[12:10] <melodie> yes yes
[12:10] <phillw> ahh.. I'll add a -
[12:10] <melodie> if it's your production machine
[12:10] <melodie> then
[12:10] <melodie> you may not have it, it seems like it's a new one in Lubuntu Wily
[12:10] <phillw> I am running wily....
[12:10] <melodie> not a -
[12:10] <phillw> have been since a1 came out
[12:10] <melodie> what's a1?
[12:11] <phillw> alpha 1
[12:11] <phillw> i always switch once alpha1 is out :)
[12:11] <melodie> I don't know that (and it's not much my problem, just if you want to install Lubuntu Wily in vbox, the one of today is ok)
[12:12] <melodie> see, the thing is, when you install htop, you start it in console:
[12:12] <melodie> then you can see the processes, you can line by threads and much more
[12:12] <phillw> phillw@piglet:~$ apt-cache policy fcitx
[12:12] <phillw> fcitx:
[12:12] <phillw>   Installed: (none)
[12:12] <phillw>   Candidate: 1:4.2.9-1
[12:12] <phillw>   Version table:
[12:12] <phillw>      1:4.2.9-1 0
[12:12] <phillw>         500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
[12:12] <melodie> phillw I don't care
[12:12] <melodie> are you listening?
[12:12] <phillw> i have htop
[12:13] <melodie> start it and observe the threads. Here everything is started twice, in vbox/lubuntu
[12:13] <melodie> that should not be
[12:13] <melodie> so either it's Wily the problem, or it's Lubuntu
[12:13] <melodie> some are even started 4 times
[12:14] <phillw> how to start ?
[12:14] <melodie> type htop in console
[12:14] <phillw> i know that bit :D
[12:14] <melodie> so what do you need to know?
[12:15] <phillw> how to start fcitx
[12:15] <melodie> there isn't anything special to do, but you can try from console
[12:15] <melodie> or console in gdb
[12:15] <melodie> as you wish
[12:15] <melodie> or restart the session and it will be there
[12:16] <phillw> phillw@piglet:~$ fcitx
[12:16] <phillw> The program 'fcitx' is currently not installed. You can install it by typing:
[12:16] <phillw> sudo apt-get install fcitx-bin
[12:16] <melodie> or from the menus
[12:16] <melodie> yes you told me already that it's not installed. I thought you are having Vbox and the Lubuntu Wily as of today or so
[12:17] <melodie> if you test in Virtualbox you can see it installed by default
[12:17] <phillw> i have wily running on my production machine, which is also pulling in proposed for wily... it's bang upto date :)
[12:17] <melodie> you don't have to rely on your own production machine to see what happens or not
[12:17] <melodie> I don't care that it's up to date, it should be a brand new install in vbox
[12:18] <melodie> otherwise you are experimenting on a machine that you are the only one to have
[12:18] <melodie> your own setup
[12:18] <phillw> don't need vbox for that... i have it on virt-manager
[12:18] <melodie> I am reinstalling again in a brand new vbox machine anyway now
[12:19] <phillw> okies... 2 X nm-applet
[12:20] <melodie> in htop, you might observe that mostly everything else is also started double
[12:20] <melodie> which is basically very wrong
[12:20] <phillw> loads of instances!!!
[12:20] <melodie> see?
[12:20] <phillw> yes, but still double applets on my production machine  with it not running.
[12:21] <melodie> there is no "but"
[12:21] <melodie> if everything runs double, it's no wonder applets come double too, that's it.
[12:21] <melodie> to check if that comes from Lubuntu or from Wily there are two ways:
[12:22] <melodie> is it the same in other editions of Ubuntu for the actual stage of Wily?
[12:22] <phillw> It is NOT running on my production machine, we have established that... I have double applets on my production machine.
[12:22] <melodie> will it be the same for Bento if I upgrade a Vivid to Wily?
[12:22] <melodie> I have established nothing, but you may send a screenshot of your htop window to some place on the web
[12:23] <melodie> started as simple user preferably
[12:23] <phillw> and on my other VM of wily 32 bit.. i have 1 a-applet and 1 n  applet....
[12:23] <melodie> ok, now I am starting the new install, if the installer get stuck I'll tell you at what stage, and will do a screenshot
[12:24] <melodie> what is different apart from that, between the 2 VM's?
[12:25] <phillw> nothing... same ISO and same VM... one was full disk, the 2nd is a side by side (guided install). It can also vary between reboots.
[12:25] <melodie> in htop you can see what initial process it has started from
[12:26] <melodie> with the "F5 sorted" key
[12:27] <melodie> I'll brb
[12:27] <melodie> and I need another Wily *buntu to test and check the double processes
[12:27] <phillw> what am i looking for in htop
[12:28] <phillw> I'll burn a 32bit DVD and grab my other laptop to do a hard-metal install on.
[12:34] <melodie> you don't need to do a hard metal install and you need to hit/click to F5 to sort the processes by thread, then you check what is the parent process of any program whose icon is double on your panel
[12:34] <phillw> i want to rule out virtualisation.
[12:36] <phillw> nm-applet has 2 entries under nm-applet
[12:37] <melodie> I don't understand "rule out virtualisation" ?
[12:38] <phillw> as I can get two different outcomes of duplicate applets (or not) under virtualisation, I think it wise to do a bare metal install.
[12:40] <melodie> ok when hiding userland threads in htop, it's much better!
[12:41] <melodie> do hide userland thread, you need to deactivate F10 in LXTerminal, then you can type F2 and in Display options you select "hide userland threads"
[12:43] <melodie> in Bento the processes are started with /sbin/init and not by "/sbin/init splash ---"
[12:43] <melodie> https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1457886
[12:43] <melodie> I just found this
[12:44] <phillw> is splash a part of the move to systemd ?
[12:44] <melodie> phillw I am now heading to the #ubuntu-bugs chan because this is as far as my know how goes
[12:44] <melodie> no it's not
[12:44] <phillw> okies
[12:44] <melodie> at #ubuntu-bugs they might be able to help me debug further
[12:45] <phillw> okay, i wish you well and thank you for taking time to investigate this bug
[12:46] <melodie> welcome
[12:46] <melodie> oh and phillw have you seen my "openbox" wiki page?
[12:47] <melodie> if not, see here? http://wiki.linuxvillage.org/doku.php?id=fr:configuration:gestionnaire_de_fenetres
[12:47] <phillw> he he ... liveCD of wily32 bit has 1 of each icon!!! this just emphasises the bug as being hit and miss...
[12:48] <phillw> looks very nice.... well done!
[12:49] <melodie> I don't like using wikis to publish docs thought, it takes too long to shape it. I'll try with Wordpress (I started)
[12:49] <melodie> I have tons of texts to publish, I need to have an efficient tool
[12:51] <phillw> I'm not familiar with WP, but it does seem to give nice layouts.... As you know I defer to Rafael on such matters :)
[12:51] <melodie> phillw when you will have finished the install, please check if the system reboots normally once the tray is opened and you will have hit "Enter"
[12:52] <phillw> oh, you want it installing ?
[12:52] <melodie> I have asked advice to #wordpress for a theme fitting the purpose, and I got a good advice
[12:52] <phillw> I just cancelled it... let me restart it!
[12:52] <melodie> isn't it what you sayd you are doing? :D
[12:52] <melodie> ok ok
[12:53] <melodie> indeed, now I see 2 nm-applets but no "â"
[12:53] <phillw> you said you were heading off... nvm.. take a few minuntes
[12:53] <melodie> this distro is fun! :D
[12:53] <melodie> no I'm not heading off, I keep my head on my shoulders.
[12:53] <phillw> this bug is 100% hair pulling out material... now reboot your VM and it may chenge
[12:53] <melodie> no I won't
[12:54] <melodie> I'll investigate with debug tools
[12:54] <melodie> then I will send the results to the devs so they have something they can use with their own scope of knowledge
[12:54] <melodie> installing guest additions
[12:55] <phillw> I suspect that there is a chase issue... the devs use virt-mananger (KVM) I know that from when I was in contact with them.
[12:57] <melodie> what is "chase"?
[12:58] <phillw> a chase condition is when two or more processes are both trying to start at the same time, one will win, but it can vary as to which one does.
[13:00] <phillw> or, that is one example... from my distant memory, which is not perfect... but you understand what i mean that it can cause different outcome each time.
[13:01] <melodie> ok a matter of priority then
[13:01] <phillw> arghhhh... i hate ubiquity!"!"!!!!!!
[13:02] <phillw> and this time, with live CD boot  ihave 2 x a applet and 2 x nm applet...
[13:02] <melodie> the fcitx comes with an autostart script which is located under /usr/bin and has a "sleep 2" in it
[13:02] <melodie> in the official Ubuntu edition?
[13:02] <melodie> just guessing as you talk about Ubiquity?
[13:02] <melodie> no
[13:02] <melodie> I confuse
[13:03] <phillw> same DVD i just booted from before where i had one of each...
[13:03] <melodie> what do you hate about Ubiquity?
[13:03] <phillw> no, i pressed the wrong button ubiquity and aborted the installation..... I'm used to server / alternate installer..
[13:05] <melodie> take your time, no rush
[13:05] <phillw> installing okay this time :)
[13:06] <phillw> you just caught me in time.. i waas about to wipe the dvd and put centos v7 onto it!
[13:08] <melodie> I named the former vm sneezy and the present one grumpy (atchoum et grincheux)
[13:09] <phillw> when it works, you can make one called happy (content)
[13:11] <melodie> Menu : Preferences > Default applications for LXSession >
[13:12] <melodie> and let's go to the "Automatic startup" tab.
[13:12] <melodie> I tried that in the preceeding install and will have a look again there now
[13:12] <phillw> i call mine by what they are.... lubuntu wily 32bit = lwily-32, xubuntu wily 64bit = xwily-64
[13:12] <phillw> bare metal install is at grub stage, so not very long
[13:13] <melodie> I see PolicyKitAuthentication Agent is not "on"
[13:13] <melodie> and ck-list-sessions lists no session at all
[13:13] <phillw> i recall issues with that....
[13:16] <melodie> what I can say for now, is that there is "something" in Lubuntu, which prevents the normal behavior of openbox : which has this openbox-autostart file, that triggers openbox-xdg-autostart to be used, if python-xdg is installed.
[13:16] <melodie> so the actual behavior of Lubuntu is not the normal one.
[13:16] <phillw> bare metal install now booted... 2 x nm applets.. no a applet
[13:16] <melodie> if you get gilir to come here to explain what he did to prevent that normal behavior, we might have a talk about that.
[13:17] <phillw> yuo would be better to email him, he rarely appears on IRC
[13:17] <melodie> and this is a detail but will be critical when openbox is the 3.6 version
[13:17] <melodie> will he answer?
[13:18] <phillw> he replies to emails, yes... mention the bug number which also has the mailing list discussion linked to it so he is fully up to date. Add in your own findings as well!
[13:20] <phillw> I've just realised why my stomach is complaining..... I have not yet had breakfast :/
[13:31] <melodie> remind me the bug number please?
[13:35] <phillw> https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1488660
[13:35] <melodie> thanks
[13:36] <phillw> please cc the lubuntu qa list as well :)
[13:39] <melodie> nope
[13:39] <melodie> I wrote in French
[13:39] <phillw> ha ha.. okay :)
[13:39] <melodie> wait for me to receive an answer from him, and I'll keep you informed, especially if that helps solving it
[13:40] <phillw> please update the bug to let people know you have done some work and have contacted Julien (in French)
[13:40] <melodie> not useful as I haven't found clues yet
[13:41] <melodie> I only know what it is not, but I think Julien has done a tweak in the system that prevents the normal openbox-autostart behavior, and for more tests I need to know what if any and then remove it
[13:42] <phillw> okay
[13:43] <melodie> so you can go have breakfast now, you worked well! :D
[13:43] <melodie> for myself, a coffee and a nap will be welcome
[13:48] <phillw> enjoy your coffee and nap :)
[13:51] <melodie> thanks
[21:49] <ianorlin> http://meetings-archive.debian.net/pub/debian-meetings/2015/debconf15/Dpkg_The_Interface.webm does this crash mplayer for other people on wily
[21:50] <ianorlin> https://bugs.launchpad.net/ubuntu/+source/mplayer2/+bug/1490200 is a bug I opened about it
[22:50] <phillw> ianorlin: phillw@piglet:~$ mplayer /home/phillw/Desktop/Dpkg*
[22:50] <phillw> MPlayer2 2.0-728-g2c378c7-4build1 (C) 2000-2012 MPlayer Team
[22:50] <phillw> Cannot open file '/home/phillw/.mplayer/input.conf': No such file or directory
[22:50] <phillw> Failed to open /home/phillw/.mplayer/input.conf.
[22:50] <phillw> Cannot open file '/etc/mplayer/input.conf': No such file or directory
[22:50] <phillw> Failed to open /etc/mplayer/input.conf.
[22:51] <phillw> Playing /home/phillw/Desktop/Dpkg_The_Interface.webm.
[22:51] <phillw> MPlayer interrupted by signal 11 in module: demux_open
[22:51] <phillw> - MPlayer crashed by bad usage of CPU/FPU/RAM.
[22:51] <phillw> btw, it plays fine with vlc.
[23:56] <ianorlin> phillw: I know it plays in vlc