[23:33] <MichaelTunnell> is Ubuntu GNOME 16.04 going to have Snappy by default
[23:33] <MichaelTunnell> ?


[12:49] <BluesKaj> Hi all
 Hello, I have a short question. I cannot seem to find a 22.04 BETA iso...is it not released yet?
[13:14] <BluesKaj> @Niggolas, https://cdimage.ubuntu.com/kubuntu/releases/22.04/beta/
 Τηανκ υοθ! (re @IrcsomeBot: <BluesKaj> @Niggolas, https://cdimage.ubuntu.com/kubuntu/releases/22.04/beta/)
 Thank you! (re @IrcsomeBot: <BluesKaj> @Niggolas, https://cdimage.ubuntu.com/kubuntu/releases/22.04/beta/)
[13:39] <BluesKaj> @Niggolas, :-)
[14:43] <tmlk> hi! Which is the default Python version in Kubuntu 21.10?
[15:27] <oerheks> python3 -v
[15:45] <sigma__> hi why i get this massage ? cannot increment value of type 'std::map<char, Counter>' (aka 'map<char, unsigned long long>')     i just try Analyzer_list[alphabet]++; Analyze is map pointer!?
[15:47] <sigma__> sorry wrong massage :)
[16:13] <tmlk> oerheks: Hi rephrase. I have both python3 and python2 in my Kubuntu installation. Python2 is the default version used by the system. "which python" resolves to a symlink to python2 binary. Is this the default or I messed somehow with my system?
[16:13] <tmlk> s/Hi/I
[16:27] <oerheks> only python3 is default, you must have installed a programm that depends on it, or cruft from upgrade
[18:54] <woenx> Hi. Maybe someone could lend me a hand. I'm new to Kubuntu (used the regular ubuntu until now) and I want to configure autofs to automatically mount a sshfs share
[18:54] <woenx> But I don't know if it's compatible. I copied my config files from my previous installation but doesn't seem to work. Maybe because KDE uses kio-fuse instead of fuse?
[18:55] <woenx> btw, I can mount the share normally by using the sshfs command, but not when using automount / autofs
[19:01] <Guest69> I'm using a library with custom allocateObj and freeObj functions. I want to wrap these in some sort of RAII unique_ptr thing (or, at least the freeObj part). What's the easiest way to to that?
[19:21] <Guest69> Oops, wrong channel.
[19:21] <woenx> I was confused xD
[19:22] <woenx> Anyway, I created a thread on the forum, with all the details
[19:22] <woenx> https://www.kubuntuforums.net/forum/currently-supported-releases/kubuntu-22-04-jammy-jellyfish/software-support-be/662079-autofs-with-sshfs-in-kubuntu-22-04
[20:27] <orca4> Hi there.
[20:29] <orca4> After a Kubuntu 21.04 reboot, my keyboard is not enabled in any graphical environment, but it sure is recognized in a plain (Ctl+Alt+F2) terminal. It used to work seamlessly before.
[20:30] <valorie> hmmm
[20:30] <valorie> that sounds like possibly a hardware issue
[20:31] <valorie> oh, except that it works in term
[20:31] <orca4> It is a USB Logitech keyboard, in a Dell desktop machine. I have rebooted several times, tried different USB ports and even another keyboard, with no success at all
[20:31] <valorie> orca4: the other day I was having a problem with my laptop cam would was not detected
[20:32] <orca4> Right now, I am in the plain (text) terminal and am able to issue any commands...
[20:32] <valorie> I figured out that there is an fn key which turns it on and off!
[20:32] <valorie> try `lsusb` -- is it listed?
[20:32] <oerheks> are you sure you are on 21.04? it is EOL, dead. But i read some more 21.10 issues with keyboard and mouse not working after reboot.
[20:32] <genii> Machiavellian designers
[20:33] <valorie> oh right, 21.04, sorry for not noticing that
[20:33] <orca4> @valorie: in fact, after the mentioned reboot, my USB mouse was not enabled either. However, after unpluggin and replugging it did start work again...
[20:34] <valorie> lsusb will list all logged in usb devices
[20:34] <valorie> so try your fn keys and see if some appear and disappear
[20:34] <valorie> and then gosh, upgrade
[20:34] <valorie> !eol
[20:37] <orca4> lsusb furnishes 3 Logitech devices: the keyboard, the mouse, the headset, 1 generic webcam and some "root hubs"...
[20:40] <valorie> so it is not the USB that is the issue
[20:40] <valorie> however, we can't support an EOL release
[20:41] <oerheks> i find no recent bugreports, but users mention this on 21.10.
[20:41] <orca4> oerheks, @ubottu: at any rate, you mean I should upgrade to which exact release? To 21.10? As far as I know 22.04 is still beta; would it be worth trying?
[20:42] <oerheks> upgrading now brings you 21.10. only if you select -d = development, you get jammy 22.04 .. out in 14 days or so
[20:43] <valorie> personally I would go for jammy, but I'm planning to do that on this machine today anyway
[20:44] <oerheks> it will be appreciated, if you find glitches/bugs.
[20:44] <orca4> If that matters, I have tried booting from older kernels, withour any success either
[20:44] <oerheks> 22.04 is LTS, stable and long term support
[20:45] <oerheks> orca4, oke, that is valuable info. you might want to file a bugerport, not sure if you can without keyboard..
[20:46] <orca4> oerheks : if I try 22.04 right now, you think this issue might get solved?
[20:46] <oerheks> if you install fresh, maybe yes
[20:48] <orca4> Hmm, in fact, I would like to preserve, by upgrading (not fresh installation) my already installed and configured packages and /home directory (which is in a separate partition)
[20:50] <orca4> So you guess upgrading to 21.10 or even 22.04 (beta), instead of a fresh install, is less likely to solve the issue?
[20:53] <orca4> The fact that in the plain terminal, the keyboard does work, but not in the login screen or (after using the virtual terminal) inside KDE, is not suggestive of just something related to perhaps some xserver-xorg-* package?
[20:55] <valorie> easiest way to file a bug is `ubuntu-bug $packagename` but as oerheks says, that will require a keyboard at some point
[20:57] <orca4> I might be able to report a bug, because I have another fully operational Ubuntu 18.04 desktop as well, physically close/next to the 21.04 problematic one. Would that work? Which package should I associated the bug with?
[21:01] <oerheks> orca4, that is the problem; ubuntu-bug collects proper info from the running system.
[21:02] <orca4> When I issue (in the 18.04 machine) the command: ubuntu-bug, the first thing it asks is the kind of problem I wanna report. Should it be: (1) Other probelm, or (2) Display (Xorg)?
[21:02] <orca4> oerheks, I see
[21:03] <oerheks> and not sure what to file the bugrepost against, what package i mean
[21:03] <orca4> Isn't there a bug reporting plain text app?
[21:03] <oerheks> no, AFAIK
[21:05] <orca4> Perhaps I am being too naive, but, after entering KDE in the problematic 21.04 machine, or by using a live cd, I have the sheer impression that everything, apart from this keyboard issue, seems to be fine...
[21:06] <oerheks> problem is; if one encounters this keyboard issue, one cannot go online to seek help or file a bugreport... so it might be a serious one, still no clue/bugreports appearing
[21:07] <orca4> Then, since I am able to run plain text commands, given sufficient expertise, should I not be able to fix everything, without having to dist-upgrade at all?
[21:10] <orca4> One last piece of info which might be relevant: when I boot from a 21.04 live usb stick, the keyboard DOES work... Does that mean something?
[21:11] <oerheks> No. you have not the update that caused this.
[21:12] <oerheks> but please, drop 21.04 .. and go for 21.10 /  22.04
[21:13] <valorie> If you want to be cautious, orca4, then burn a thumbdrive with 22.04 beta and try it out
[21:13] <valorie> if it works, you are golden
[21:14] <valorie> then you can either upgrade (twice) or just do a fresh install
[21:15] <valorie> using an eol is dangerous, because you are not getting even security updates
[21:16] <oerheks> updates would mention there is a new version available.
[21:18] <orca4> Ok I see. I guess I have nothing to lose, by then trying to upgrade twice, as valorie says: 21.04 -> 21.10 and then 21.10 -> 22.04 beta. Is it just a matter of changing the sources.list file and issuing apt upgrade, then apt dist-upgrade?
[21:23] <orca4> Should I be able to do the twice upgrade in a plain text terminal?
[21:37] <orca4> Thank you all!!


[01:19] <Steedalion> I added a bug. https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439
[01:44] -lugito:#lubuntu-devel- [rMANUAL31e1a6a245ef: Fix a typo.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rMANUAL31e1a6a245ef
[01:47] -lugito:#lubuntu-devel- [rMANUALfe28a2629fde: Keyboard changes updated Deleted some artifacts] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUALfe28a2629fde
[01:47] -lugito:#lubuntu-devel- [rMANUALb3e37473f7a9: Merge branch 'master' of ssh://phab.lubuntu.me:2222/source/lubuntu-manual] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUALb3e37473f7a9
[01:47] -lugito:#lubuntu-devel- [rMANUAL5e2b1d61b1ef: typos] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUAL5e2b1d61b1ef
[01:47] -lugito:#lubuntu-devel- [rMANUALdc2389ecd960: Merge remote-tracking branch 'Steedalion/master'] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rMANUALdc2389ecd960
[02:47] <wxl> don't mind me
[02:47] <wxl> !hashes
[03:25] <wxl> @tsimonq2: didn't you fix this? could you update if so? https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799855
 @wxl [<wxl> @tsimonq2: didn't you fix this? could you update if so? https://bugs.launc …], See the task for info
 I updated it today
[03:26] <wxl> k
 About to go to bed
 Last call for things I should look at wxl
[03:32] <wxl> maybe one
[03:32] <wxl> shot in the dark though
[03:32] <wxl> do you remember where in lubuntu this was first reported? i think it's still an issue despite the state of thi sbug https://github.com/calamares/calamares/issues/712
 I don't, sorry.
 I know it was by that one Scott guy or whatever
 The guy who put all the bugs in one
 Scott Cowles Jacob is his name?
 I dunno
 Anyway, sleep now
 Bai
[03:34] <wxl> see you
[05:28] -lugito:#lubuntu-devel- [rMANUAL3e83dac1ee74: Add code:: for the command line and make lxqt-sudo] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL3e83dac1ee74
[05:35] -lugito:#lubuntu-devel- [rMANUAL707a856b8a73: Add ls to basic commands in appendix C] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL707a856b8a73
[06:54] -lugito:#lubuntu-devel- [T88: Lugito should do diffs] doc-E-brown (Ben Johnston) commented on the task: https://phab.lubuntu.me/T88#3106
 Is it possible to remove all elements of xubuntu,after installing lubuntu desktop on it
 @v4vnc [Is it possible to remove all elements of xubuntu,after installing lubuntu deskto …], Means replacing all xubuntu programs with lubuntu desktop
 Why don‘t you make a clean install?
 Lubuntu is not working after installing,because of some kernel and driver problem
[14:00] <apt-ghetto> What does it mean "Lubuntu is not working after installing"?
 My PC is too old,I tried to install lubuntu but it shows but it didn't worked
 @v4vnc [Means replacing all xubuntu programs with lubuntu desktop], Tell me about it
[14:04] <apt-ghetto> After that you have installed Xubuntu?
 @apt-ghetto [<apt-ghetto> After that you have installed Xubuntu?], Yeah
 It works well but it is slow
[14:06] <apt-ghetto> 18.10 or 18.04?
 18.04
[14:10] <apt-ghetto> What CPU, RAM, graphic card?
 Pentium 4
 1 GB ram
[14:12] <apt-ghetto> Should be enough to run XFCE or LXDE
 Ohk
[14:13] <apt-ghetto> Can you describe the kernel and driver problems?
 @v4vnc [Means replacing all xubuntu programs with lubuntu desktop], Is this possible or not
 @apt-ghetto [<apt-ghetto> Can you describe the kernel and driver problems?], No I don't want to install that lubuntu again
 @v4vnc [Means replacing all xubuntu programs with lubuntu desktop], Tell me about this
[14:14] <apt-ghetto> you can remove all unwanted packages
[14:14] <apt-ghetto> and maybe you have to reinstall some dependencies needed by lxde
 @apt-ghetto [<apt-ghetto> you can remove all unwanted packages], How to do thay
 That
[14:17] <apt-ghetto> To remove mousepad, type `sudo apt remove mousepad` or `sudo apt purge mousepad`
[14:20] <apt-ghetto> you can remove also the `xubuntu-desktop` package, but this is a metapackage
 @shar dan [lubuntu 19.04 alpha ?], What about it?
 @shar dan [lubuntu 19.04 alpha ?], We're in pre-alpha right now.
 It's at https://lubuntu.me/downloads if you want it
 I'll declare Alpha when things are in place for 19.04.
 @shar dan [why is not on lubuntu.net  ... or cdimage], We don't control Lubuntu.net.
 It's on cdimage though; if you went to https://lubuntu.me/downloads you'd see that we link to cdimage ISOs
 Not yet in 19.04 but relatively soon.
 @shar dan [be problems ?], Not that I know of, but I wouldn't recommend it.
[18:08] <apt-ghetto> @tsimonq2 The grub.cfg in the iso, where does it come from?
[18:08] <tsimonq2> apt-ghetto: Calamares.
[18:08] <tsimonq2> I'm likely going to be redoing Calamares' grub handling because apparently Adam and Steve seem to think that's a Bad Thing.
[18:09] <apt-ghetto> I am asking because of T106
[18:09]  * tsimonq2 kicks lugito
[18:09] <tsimonq2> https://phab.lubuntu.me/T106
[18:09] -lugito:#lubuntu-devel- [Medium, Open] theme GRUB: https://phab.lubuntu.me/T106
[18:09] <tsimonq2> ahh
[18:09] <tsimonq2> got it
[18:09] <tsimonq2> apt-ghetto: Yeah, normally that comes from one of our GRUB packages in the archive.
[18:14] <apt-ghetto> Is it possible to change the grub.cfg only for the lubuntu iso or does it mean, that changing the grub.cfg will be also changed in the whole ubuntu universe?
[18:15] <tsimonq2> I can't definitively answer that question yet, sorry.
[18:15] <apt-ghetto> No problem
[18:40] -lugito:#lubuntu-devel- [rWELCOMEe0cb7ab14495: Added mockup folder with welcome mockups.] TheWendyPower (Wendy Hill) committed: https://phab.lubuntu.me/rWELCOMEe0cb7ab14495
 (Document) https://telegram.lubuntu.me/tEEUZUEt/file_4575.png
 Oooh, I like it.
 Is there anything else that should be on that fist window of the welcome?
 Very cool!
[19:59] -lugito:#lubuntu-devel- [rLUGITO165c866a5d5a: Multiple changes, cleanup, etc.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO165c866a5d5a
[23:06] -queuebot:#lubuntu-devel- Unapproved: calamares-settings-ubuntu (disco-proposed/universe) [29 => 30] (lubuntu)
[23:11] -lugito:#lubuntu-devel- [T152: Disco Dingo Wallpaper] TheWendyPower (Wendy Hill) commented on the task: https://phab.lubuntu.me/T152#3107
[23:11] -lugito:#lubuntu-devel- [rMANUALecff73155583: Start appendix A and give title to openbox shortcuts and put in toctree] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALecff73155583
[23:14] -lugito:#lubuntu-devel- [rMANUAL140e88252d11: Add () and copy/paste to Kcalc] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL140e88252d11
[23:14] -lugito:#lubuntu-devel- [rMANUALc46d3f8c5461: Add search and jump to line in featherpad] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALc46d3f8c5461
[23:15] -lugito:#lubuntu-devel- [rCALASETTINGSaddf582ce8e0: Change the desktop file from 18.10 to 19.04.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rCALASETTINGSaddf582ce8e0
[23:15] -lugito:#lubuntu-devel- [rCALASETTINGS16c302d2fa2b: Upload to Disco.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rCALASETTINGS16c302d2fa2b
[23:15] <mpmc> doesn't lugito text-merge commits :o
[23:16] <tsimonq2> Hm?
[23:17] <mpmc> Instead of announcing a set of recent commits it puts out individual messages
[23:17] <tsimonq2> Yeah, no.
[23:17] <tsimonq2> That's intentional.
[23:17] <mpmc> How come?
[23:17] <tsimonq2> Because when I push five commits, I want five notifications.
[23:18] <tsimonq2> I don't want to have to go to a webpage to see all five commits.
[23:18] <tsimonq2> It's an intentional design decision when I wrote the script. :P
[23:18] <tsimonq2> "It's a feature, not a bug!" >:D
[23:18] <mpmc> tsimonq2: Why not have a setting per user? :p
[23:19] <tsimonq2> Because I'm the user. :P
[23:19] <mpmc> So no one else uses ligito?
[23:19] <mpmc> lugito*
[23:19] <tsimonq2> Nope, it was written for Lubuntu, by me. :P
[23:19] <tsimonq2> It is in no other channels.
[23:19] <tsimonq2> I accept PRs though.
[23:20] <mpmc> I mean for other people in Lubuntu that uses it, you can't be the only one.
[23:20] <tsimonq2> ...it's a notification bot.
[23:20] <tsimonq2> It does nothing more.
[23:20] <tsimonq2> So, the "user" is #lubuntu-devel.
[23:21] <tsimonq2> (Well, it also does bug commenting, but heh...)
[23:23] -lugito:#lubuntu-devel- [rNEWRELa8b8d920efe7: Extend the checklist and write setup-phab.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rNEWRELa8b8d920efe7
[23:24] <mpmc> fair enough.
[23:24] -lugito:#lubuntu-devel- [T156: Write a script to open the archive infra for us] tsimonq2 (Simon Quigley) commented on the task: https://phab.lubuntu.me/T156#3115
[23:28] <mpmc> Lol @ cat facts.
[23:28] <tsimonq2> ¯\_(ツ)_/¯
[23:28] <tsimonq2> Why not? XD
[23:30] -lugito:#lubuntu-devel- [rMANUAL4f0e94e898d0: Added keyboard shortcuts section. 	Added table of Openbox keys 	Added reference…] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUAL4f0e94e898d0
[23:30] -lugito:#lubuntu-devel- [rMANUAL1e16dff5b48f: Made some minor changes in Shortcut Keys 	Renamed heading to 'shortcut keys' ->…] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUAL1e16dff5b48f
[23:30] -lugito:#lubuntu-devel- [rMANUALc52c087d3cab: Removed test file.] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUALc52c087d3cab
[23:30] -lugito:#lubuntu-devel- [rMANUAL4a8b279760c1: Indexed keyboard shortcuts, Appendix F] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUAL4a8b279760c1
[23:30] -lugito:#lubuntu-devel- [rMANUALf17fe22d8142: Merge branch 'master' into keyboardshortcuts] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUALf17fe22d8142
[23:31] -lugito:#lubuntu-devel- [rMANUAL987927d12a63: Fix installation of packages] Diffusion committed: https://phab.lubuntu.me/rMANUAL987927d12a63
[23:31] -lugito:#lubuntu-devel- [rMANUAL84917b44ccf0: Merge remote-tracking branch 'apt-ghetto/installfix'] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rMANUAL84917b44ccf0
[23:31] -lugito:#lubuntu-devel- [rMANUAL4b1aaccad4bb: Fix Typo in chapter 3] Diffusion committed: https://phab.lubuntu.me/rMANUAL4b1aaccad4bb
[23:31] -lugito:#lubuntu-devel- [rMANUAL081ea0adecc0: Merge remote-tracking branch 'apt-ghetto/preferencetypo'] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rMANUAL081ea0adecc0
[23:31] -lugito:#lubuntu-devel- [rMANUALf633a1b57cbb: Merge branch 'master' of ssh://phab.lubuntu.me:2222/source/lubuntu-manual into…] Steedalion (Steed) committed: https://phab.lubuntu.me/rMANUALf633a1b57cbb
[23:31] -lugito:#lubuntu-devel- [rMANUALdd7f724bc318: Merge remote-tracking branch 'Steedalion/keyboardshortcuts'] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rMANUALdd7f724bc318
[23:31] <mpmc> tsimonq2: do you use Lubuntu as your daily driver? :p
[23:31] <tsimonq2> mpmc: I do.
[23:31] <tsimonq2> mpmc: The development release, always.
[23:36] <mpmc> So many open tasks. Nice to see the git login working =D
[23:36] <tsimonq2> For sure, we've been busy :)
[23:37] <tsimonq2> If you can see it, take a look: https://phab.lubuntu.me/maniphest/report/burn/
[23:44] <mpmc> tsimonq2: Any reason why the welcome centre is written in C# rather than something more universal like Python?
[23:44] <tsimonq2> mpmc: It's written in C++, which is about as universal as you can get.
[23:45] <mpmc> I always get c# & c++ confused xD
[23:45] <tsimonq2> ah :)
[23:45] <mpmc> still, would get a lot more people on it (perhaps me) if it was Python lol.
[23:47] <tsimonq2> ¯\_(ツ)_/¯
[23:47] <mpmc> You really love that ascii :p
[23:47] <tsimonq2> mpmc: We do have a lot of stuff written in Python (like Lugito) so you aren't out of things to do if you wanted to help. :P
[23:47] <tsimonq2> ¯\_(ツ)_/¯
[23:50] <mpmc> tsimonq2: hehe. A simple nice looking html page included would work just as well imo. perhaps even an icon to launch it in the default browser.
[23:50] <mpmc> But what do I know :)


[01:21] <primefalcon> quick question for all, is there a way to sync liferea using ubuntuone?
[01:22] <CardinalFang> primefalcon, what is it you want to sync?
[01:22] <primefalcon> the feedlist
[01:25] <CardinalFang> primefalcon, Hrm.  Well, you could perhaps copy the liferea config into the Ubuntu One mass storage system.  Or there's the database that works with Ubuntu One, which one could port liferea to use.  The first is doable tonight.  The latter is what you might be using in several months.
[01:26] <primefalcon> so there's more work going on with a database sync, nice
[01:27] <primefalcon> in the meantime I guess I'll do a cronscript, thx for the info :-)
[01:47] <rtgz> nailed #491777. Time to Z-z-zzz :)
[01:47] <rtgz> and #479475
[01:48] <rtgz> bug #479475
[01:48] <rtgz> Bye everyone and have a nice weekend (it actually started here 4 hours ago...)
[04:37] <ElRola> hello
[05:49] <hackel> Oh goodie...  Today I've got another 2777 .u1conflict files to deal with.  This is getting really old...
[07:29] <zeltak> hya. anyone knows how to stop ubuntu one from asking for a password after every reboot by any chance?
[14:32] <AceKing> I'm having a problem when I start Ubuntu One. It has a red "X" through the icon in the taskbar. When I click on it, it errors out. I tried sending an error report and I got an email that says there was an update that fixed this problem, but I'm still getting the red "X". Anyone know how to fix this?
[14:34] <AceKing> Anyone in here?
[19:40] <rtgz> Is there any dev willing to sacrifice 10 minutes of his own time to help a novice-deb packager find out where to get the debian/ directory from for trunk ubuntuone-client ?
[19:46] <rtgz> anybody... debian/ dir for ubuntuone-client? where it comes from?
[23:55] <rtgz> shareoffer page is broken
[23:55] <rtgz> and all share-related stuff for webui is broken as well, giving internal server record
[23:55] <rtgz> *error
[23:56] <rtgz> just a notification, will run in circles, scream and shout on Monday if not fixed.
[23:58] <chatZilla_> will there be an Ubuntu One for Xubuntu? or LUbuntu?


[00:09] <fta> chrisccoulson_, did something change wrt the preferred apps?
[00:10] <chrisccoulson_> fta - not recently AFAIK, how come?
[00:11] <fta> chrisccoulson_, chromium is now complaining it's no longer the preferred browser here, confirmed by BUGabundo
[00:11] <fta> was fine until yesterday
[00:13] <chrisccoulson_> fta - oh, i see that too
[00:16] <chrisccoulson_> oh, i saw it because i opened gnome-default-application-properties, and that tramples over the gconf settings
[00:17] <fta> ?
[00:18] <chrisccoulson_> gnome-default-application-properties writes the gio config to gconf, to keep everything in sync
[00:18] <chrisccoulson_> but chromium isn't using th gio settings
[00:18] <chrisccoulson_> it's using xdg-settings isn't it?
[00:18] <fta> yes
[00:19] <fta> xdg-mime irrc
[00:23] <chrisccoulson_> fta - ok, i got release team ACK to backport the xdg-utils changes to fix this
[00:23] <chrisccoulson_> i'll do it tomorrow
[00:24] <fta> good, even if i still don't understand what changed
[00:26] <chrisccoulson_> i'm not sure what's changed in the last few days, but it should never have started working really ;)
[00:27] <fta> $ xdg-settings check default-web-browser chromium-browser.desktop
[00:27] <fta> yes
[00:38] <fta> hm, just rebooted, i now have some artifacts from the widgets in chromium
[11:57] <fta> chrisccoulson, ch trunk bumped Breakpad to r786, what was missing to have it working? i lost track :(
[12:07] <Guest94759> Hi, everyone! I want to compile firefox with DWARF2 debugging information. What shall I do to solve this problem? Must I modify the makefile?
[12:38] <fta> chrisccoulson, found the regression for the preferred browser in ch trunk: http://codereview.chromium.org/6793034  it's what you expected i guess
[12:39] <chrisccoulson> fta - re, breakpad and chromium - kees has fixed all of the kernel bugs now, but chromium still isn't working :(
[12:40] <chrisccoulson> i'm stuck atm, because i can't reproduce it in strace, which would really help
[12:40] <chrisccoulson> i pinged evan, and strace only works if you run with --no-sandbox
[12:40] <chrisccoulson> and of course, crash reporting works fine then ;)
[12:41] <chrisccoulson> the only way i'm going to be able to debug it is to do a build of chromium with some debug printfs in there so i can figure out exactly why it fails ;)
[12:43] <chrisccoulson> fta - about xdg-utils, i'll update our version today which should hopefully fix the browser check issues
[12:43] <chrisccoulson> i thought that had already been done, i'm not sure why it dropped off the radar :(
[13:17] <fta> chrisccoulson, maybe try a debug build. I have a knob in d/rules
[20:15] <fta> chrisccoulson, not sure why it failed last night, but i just respun the bot for ff-trunk and the upload worked this time
[21:01] <chrisccoulson> fta - thanks. i was going to ask you that too actually :)
[21:03] <fta> chrisccoulson, just read the TB minutes, are they really considering backing off unity as default??
[21:19] <fta> micahg, hi, any update on the last chromium update?
[21:19] <fta> it's been a while now :P
[21:21] <micahg> ugh, no, but it seems that the detect flag isn't good enough, I'll complete the testing today which should tell me if we're already affected or not
[22:05] <chrisccoulson> m_conley_away, did bug 734837 fix your issue with the invisible entries in the menu bar?
[22:26] <fta> uh, the new compiz crashed
[22:26] <fta> it's been a while
[22:26] <fta> bamfdaemon too
[22:42] <micahg> chrisccoulson: someone on m.d.a.firefox is proposing rewriting Firefox in Java :)
[22:45] <chrisccoulson> lol
[23:02] <m_conley> chrisccoulson: ping
[23:02] <chrisccoulson> hi m_conley
[23:03] <m_conley> chrisccoulson: hey!  I'm about to try out the globalmenu extension in TB.  I'll tell you how it goes. :)
[23:03] <chrisccoulson> excellent, thanks!
[23:03] <m_conley> chrisccoulson: I'm at the all-hands in Mountain View, and we're talking about the new release cycle, and how it affects TB
[23:03] <m_conley> chrisccoulson: can I assume you've heard about the new release cycle?
[23:03] <chrisccoulson> cool, i'd be interested to know how that turns out
[23:03] <chrisccoulson> yeah, i know about it for firefox, but i'm still unclear about how it's actually going to work
[23:04] <m_conley> chrisccoulson: see - http://mozilla.github.com/process-releases/draft/development_overview/
[23:04] <m_conley> chrisccoulson: how it affects TB, and Linux distros in currently being discussed here
[23:04] <chrisccoulson> m_conley, will you test the globalmenu-extension provided in the archive, or do you build it yourself? i haven't actually pushed the fix to bzr yet, as the branch seems to have stopped working :(
[23:04] <m_conley> er "is"
[23:04] <m_conley> chrisccoulson: hm - I was about to try the one in the archive
[23:05] <chrisccoulson> that's ok then :)
[23:05] <chrisccoulson> i think we're mostly ok with the release process. what i'm totally unclear about is how releases are created from the different branches
[23:05] <micahg> m_conley: is there a place anywhere to vote for some type of LTS branch for linux distros/derivitives?
[23:06] <m_conley> micahg: not as far as I can tell, no
[23:07] <chrisccoulson> m_conley, have you had much feedback from other distros?
[23:07] <m_conley> chrisccoulson: not personally, no.  Other Mozilla folk may have
[23:08] <m_conley> micahg: there might be infrastructure for that down the line
[23:08] <m_conley> or something similar
[23:09] <kbrosnan> long lived versions are not on the plan atm
[23:10] <m_conley> chrisccoulson: I'm sort of the Linux representative in this "new release cycle" meeting - but I don't think I have a total handle on what's at stake here.  I understand the LTS issue, but is there anything else I should be bringing up?
[23:11] <chrisccoulson> the LTS issue only really affects xulrunner, because we have to maintain a bunch of apps using it. but, from the POV of firefox and thunderbird, i think we can live without it ;)
[23:11] <kbrosnan> but feedback from distros would be intresting as of right now going forward from 5 there are no plans to ship any dot updates
[23:11] <micahg> m_conley: well, major version bumps as opposed to point releases with bugfixes are harder in terms of QA for stable releases
[23:12] <chrisccoulson> we don't do crazy things like building FF-on-XR like other distro's do ;)
[23:12] <micahg> chrisccoulson: I'd prefer to limit it just to Firefox if possible
[23:12] <micahg> QA burden is higher for major version bumps
[23:12] <chrisccoulson> micahg, the QA stuff is exactly why we're running the full test-suite now ;)
[23:12] <micahg> chrisccoulson: for thunderbird as well?
[23:13] <chrisccoulson> (although, we currently don't do anything with the output of that, but we should be)
[23:13] <chrisccoulson> micahg - not yet. i wasn't going to start running that until we update to 3.3
[23:13] <chrisccoulson> kbrosnan, i think most of the questions i have really are just minor details, but affect my workflow quite a bit. i'll write them down at some point :)
[23:14] <micahg> kbrosnan: well, I'm currently considering dropping any xulrunner app that accesses insecure content from the repo since porting every 6 weeks in a stable release is out of the question
[23:17] <kbrosnan> micahg: have a query or a wag to the number of packages effected?
[23:17] <chrisccoulson> kbrosnan, https://wiki.ubuntu.com/DesktopTeam/Specs/Natty/Firefox4/XULRunner20Transition would be a good place to start
[23:18] <chrisccoulson> (note, that contains both mozjs and xpcom consumers, and we've already resolved the mozjs issue)
[23:19] <chrisccoulson> we provide a separate libmozjs package now, and i'm going to turn off --enable-shared-js in our xulrunner build at some point soon
[23:19] <micahg> kbrosnan: I think it's only about 10, maybe less at this point, I can get an official count later this evening
[23:19] <micahg> but eclipse is on the list
[23:20] <kbrosnan> yeah they are a tough case
[23:21] <m_conley> chrisccoulson: ok, cool - let me know if you have any questions you want me to bring up. :)
[23:22] <kbrosnan> smedberg has said unless some community members/orgs have an intrest in gtkmozembed and other embedding tools that are in the process of being dropped from support
[23:22] <chrisccoulson> m_conley, thanks!
[23:22] <kbrosnan> uggh that was a lot less clear than i thought
[23:22] <chrisccoulson> m_conley, did you see http://www.omgubuntu.co.uk/2011/04/uds-p-planning-ubuntu-12-04-to-be-held-in-orlando-again/ btw?
[23:22] <micahg> kbrosnan:  we have 7 apps according to the wiki using that
[23:22] <chrisccoulson> m_conley, if you can't make it to budapest ;)
[23:23] <chrisccoulson> it would be nice to see some firefox guys at a UDS too ;)
[23:23] <chrisccoulson> kbrosnan, micahg - we don't really have that much using gtkmozembed
[23:23] <chrisccoulson> the only things i can think of are:
[23:23] <chrisccoulson> chmsee, which already has WIP webkit support
[23:24] <m_conley> chrisccoulson: i'm working on budapest.  :D  I'll let you know.
[23:24] <chrisccoulson> gnome-python-extras - which is deprecated now anyway, now we have PyGI, so that's going to disappear entirely next cycle anyway
[23:24] <chrisccoulson> that's all i can think of right now ;)
[23:24] <micahg> chrisccoulson: python-gtkmozembed was that stuff I was looking at, forgot about chmsee :)
[23:24] <chrisccoulson> m_conley, awesome!
[23:24] <chrisccoulson> micahg - python-gtkmozembed is going to disappear next cycle
[23:24] <chrisccoulson> it's dead ;)
[23:26] <chrisccoulson> yeah, so just 2 things in the archive using gtkmozembed
[23:26] <chrisccoulson> i'm really not all that concerned about that :)
[23:41] <BUGabundo> evening


[12:01] <mdales> is it possible to have upstart start job b if job a failed?
[12:10] <Keybuk> yes
[12:19] <keesj> hi
[12:21] <Keybuk> mdales: the stopping and stopped events have arguments saying that it failed, what failed and why
[12:21] <mdales> ah, excellent
[12:21] <mdales> is that in the version that's in gutsy?
[12:22] <mdales> I was reading up on jobfailedevent, but I assume that's not there at the moment.
[12:22] <mdales> thanks for the info
[12:23] <Keybuk> it's there
[12:23] <Keybuk> job-failed-event was implemented in 0.3.x
[12:23] <mdales> ah
[12:23] <mdales> w00t
[12:33] <keesj> I have a job that was started and exite sucessfully , it is not a rewawn job , but I would like the job to remain in "start(ed)" status or at least would like to know that is was started
[12:33] <keesj> (I currently have a while sds ; sleep 10 ;  to keep it running
[12:53] <Keybuk> I'm not sure I follow
[12:54] <keesj> :P
[12:55] <Keybuk> you have a job
[12:55] <Keybuk> and you want that job to always be running?
[12:56] <keesj> what I really want to know is if is was stated regardless of whether it is still running
[12:56] <Keybuk> if it was started, the goal will always be start?
[12:57] <keesj> much like the mount-kernel-filesystem job
[12:57] <Keybuk> usual way for that kind of thing is to put the work in the pre-start bit of the job
[12:57] <keesj> Keybuk: what is the "goal" of a job?
[12:58] <Keybuk> spore scott% sudo status tty1
[12:58] <Keybuk> tty1 (start) running, process 4576
[12:58] <Keybuk> the goal is start, which means Upstart will attempt to keep the job running
[12:58] <Keybuk> if the goal is stop, Upstart will attempt to keep the job _from_ running
[12:58] <Keybuk> goal is changed to start by events or manual command
[12:59] <Keybuk> goal is changed to stop by events, manual command and the main process exiting (unless respawn and not normal exit)
[12:59] <keesj> yes but I don't want it to be running, even if I call start mount-kernel-filesystems
[13:00] <Keybuk> jdong: I was thinking about whether there should be the option of "sticky" jobs
[13:00] <Keybuk> that stayed running even after the process exited
[13:00] <Keybuk> but I couldn't decide whether that was any different from what you were doing, and just doing the work in pre-start
[13:00] <keesj> after that (because the jobs is no respawn) the status is stop
[13:00] <keesj> I would like it to be something else  :p
[13:01] <Keybuk> respawn would keep it at start
[13:01] <Keybuk> (though you would still get stopping/stopped/starting/started events each time it exited)
[13:02] <keesj> but I don't want that. I want the job to finish gracefully and the status to remain on something else then "stopped"
[13:02] <Keybuk> the best way to do that is to put your "job" in pre-start
[13:02] <Keybuk> it'll be run when you start the job, and the job will stay in running (since there's no script/exec) until otherwise stopped
[13:03] <keesj> the that sounds very sexy!
[13:03] <keesj> let me try that!
[13:09] <Keybuk> it's an interesting pattern
[13:27] <keesj> I can not say how happy I am ! it is working!
[13:37] <keesj> well kinda ...
[13:40] <keesj> apparently I can not simply start such a service using emit (with no --no-wait)
[13:40] <keesj> perhaps it is missing some events
[13:40] <Keybuk> start?
[13:40]  * Keybuk really must fix that confusion
[13:41] <Keybuk> if you have /etc/event.d/foo
[13:41] <Keybuk> then the right way to start it is just "start foo"
[13:41] <Keybuk> emit foo won't do anything unless foo has "start on foo" in its job definition
[13:47] <keesj> yes , I have things like start on start_boot_mode_select
[14:02] <keesj> also with start foo I have to use --no-wait, , I am using 0.3.8