[01:38] <bluesabre> Python 2.7 EOL has been moved to 2020
[01:42] <Unit193> That's good, I use stuff with py2.
[02:18] <sidi-valencia> sad
[02:19] <sidi-valencia> please dont write *new* code in py2 :(
[02:19] <Unit193> I don't wite it, I use existing and hack on it.
[02:50] <Logan_> Unit193: your hacking should include running 2to3 :P
[03:18] <stormlink> anyone around?
[03:23] <Logan_> stormlink: yeah, what's up?
[03:24] <stormlink> I've been lurking in the dev list for some time now, I want to start actually helping around
[03:24] <stormlink> not sure where to really start
[03:24] <stormlink> I do Python
[03:27] <Logan_> ali1234?
[03:33] <jphilipz> hi all, just found a bug in xfce that effects xubuntu and wanted to bring it to your attention
[03:36] <jphilipz> it involves thunar's calculation of file sizes
[03:40] <jphilipz> thunar is dividing by 1000 rather than 1024 when calculating kilobytes, megabytes and gigabytes
[03:40] <jphilipz> https://bugzilla.xfce.org/show_bug.cgi?id=10864
[10:36] <brainwash> interesting.. firefox launches significantly faster without irqbalance doing its magic in the background (sudo service irqbalance stop)
[10:37] <brainwash> fresh boot mainly
[10:37] <bluesabre> yay, I finally recreated the crash I've been trying to make knome do
[10:37] <knome> yay ;)
[10:37] <knome> so i don't need to?!
[10:37] <brainwash> buglibre?
[10:38] <bluesabre> oh
[10:38] <bluesabre> that stings
[10:38] <bluesabre> :'(
[10:38] <brainwash> :P
[10:38] <knome> lol
[10:38] <knome> i can though
[10:38] <knome> i could do that relatively soon
[10:38] <knome> wife's laptop is free
[10:38] <brainwash> coding a menu editor seems to be a tough job
[10:38] <bluesabre> I've got it now
[10:38] <bluesabre> first I had to get rid of the xubuntu menu files
[10:39] <bluesabre> the bug originates from the upstream xfce one
[10:39] <brainwash> the default Xfce session one?
[10:39] <bluesabre> /etc/xdg/menus/xfce-applications.menu
[10:39] <brainwash> how do they get mixed?
[10:40] <bluesabre> dunno
[12:17] <bluesabre> knome: latest commit should fix your issue
[12:17] <bluesabre> (re: menulibre)
[12:18]  * bluesabre downloads all ubuntu flavors for additional testing
[12:19] <knome> with the broken menu file, or should not be able to reproduce?
[12:43] <bluesabre> it probably won't work with the broken menu file
[12:43] <bluesabre> :(
[12:43] <bluesabre> but it will not break future menu files
[12:44] <bluesabre> I hardened the code
[12:44] <bluesabre> so, the reason it crashes is because I was not giving the correct name to xfce-settings.directory
[12:45] <bluesabre> so with the parent file, it was being added, and with the child file, it was being added again
[12:45] <bluesabre> (with a different name)
[12:45] <bluesabre> this caused gnome-menus to die
[12:47] <knome> >__<
[12:57] <bluesabre> and I never caught this before because I was using the xubuntu menu file
[12:57] <bluesabre> >.<
[12:59] <amigamagic> the shift-control-cursor_key thing with abiword was indeed a bug of the current 3.0.0 version: http://bugzilla.abisource.com/show_bug.cgi?id=13596
[13:00] <sidi-valencia> https://github.com/Sidnioulz/SandboxUtils/tree/master/mockups/sfcd-autocompletion
[13:00] <sidi-valencia> oops
[13:00] <sidi-valencia> that was for shimmer
[13:04] <amigamagic> anyway I think very few people use abiword instead of libreoffice write (maybe xubuntu should switch from abiword -> write?). I'm using it now (abiword) to write some notes, because I'm too lazy to install libreoffice... :D
[13:09] <amigamagic> hey, people, do you know that linux kernel 3.13.x branch is now in its EOL stage (check https://www.kernel.org/)? This means no more support and bugfixes from kernel mantainers...  Shouldn't we switch to a supported stable branch like the 3.14.x one?
[13:09] <brainwash> no, the ubuntu guys will maintain 3.13
[13:09] <knome> amigamagic, we're not the team that supports the kernel whatsoever
[13:11] <amigamagic> brainwash, so the ubuntu guys will mantain the kernel 3.13 line their self with stuff like bugfixes, security fixes, etc., albeit the main developers of the kernel don't support it anymore?
[13:12] <brainwash> yes
[13:12] <brainwash> it's a kernel with a custom config and ubuntu specific patches after all
[13:16] <amigamagic> ok, thanks for the info. I read from the changelog that 3.14 kernel has a better support for last intel integrated gpu so I would like to try it on a machine (Intel Xeon with integrated intel GPU on the same die) that has some little graphics troubles with previous kernel.
[13:16] <amigamagic> Do you think I can try 3.14 kernel on ubuntu?
[13:16] <amigamagic> Is there some backport repository or something like that?
[13:17] <bluesabre> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[13:17] <bluesabre> unsupported, but better than installing yourself
[13:17] <amigamagic> thanks bluesabre!
[13:17] <bluesabre> when the next ubuntu release is available, it's kernel version will be available to trusty as well
[13:18] <bluesabre> I used those packages in 13.10 because my laptop needed the newest
[13:19] <amigamagic> sorry for the very ignorant question, but how can I install this on a ubuntu machine? linux-image-3.14.1-031401-generic_3.14.1-031401.201404141220_amd64.deb
[13:20] <amigamagic> I double click on it and it does it all by himself?
[13:22] <bluesabre> download each of the files for your architecture
[13:22] <bluesabre> then open a terminal to your Downloads folder
[13:22] <bluesabre> and do
[13:23] <bluesabre> sudo dpkg -i linux*.deb
[13:23] <bluesabre> also, grab the _all one as well
[13:23] <bluesabre> this should cover any bases, including dkms modules
[13:24] <amigamagic> very thanks, bluesabre ;)
[13:24] <bluesabre> oh wait
[13:24] <brainwash> but it does not include new firmware files
[13:24] <bluesabre> don't grab the lowlatency ones
[13:24] <bluesabre> right, but for most things they are set up with dkms, so they will be set up when the kernel is installed
[13:24] <sidi-valencia> amigamagic, brainwash yes you should switch D:
[13:25] <brainwash> distro? or what? :P
[13:25] <sidi-valencia> ahah
[13:25] <sidi-valencia> *i* did not say that
[13:25] <sidi-valencia> kernel
[13:25] <bluesabre> regardless, your previous kernel versions will remain installed, and you can switch between them in grub
[13:25] <brainwash> ah, still running 3.11 on my main system
[13:26] <amigamagic> brainwash, what's that new firmware files thing?
[13:26] <sidi-valencia> amigamagic, there is a PPA somewhere from ubuntu-kernel with the latest kernels
[13:27] <brainwash> amigamagic: ignore it right now
[13:27] <brainwash> you might need some new firmware files if you are using brand new hardware
[13:28] <brainwash> but the kernel install routine should tell you what's missing
[13:29] <amigamagic> do you think something that now works with an ubuntu 12.04 lts distro, could break after installing the kernel 3.14 ?
[13:29] <sidi-valencia> amigamagic, no?
[13:29] <sidi-valencia> unless there are bugs, why would it break
[13:29] <sidi-valencia> the two issues you can get are: bugs and no-longer-supported firmware
[13:29] <amigamagic> I mean, some hardware that before worked and now it is not more recognized... It's possible?
[13:30] <amigamagic> ethernet cards, gpu, etc.
[13:30] <sidi-valencia> yes
[13:30] <brainwash> everything is possible
[13:30] <sidi-valencia> if there is a proprietary driver
[13:30] <sidi-valencia> and they didnt update it
[13:30] <sidi-valencia> it could be possible
[13:45] <amigamagic> ok so I should only try... thanks
[19:30] <brainwash> elfy: bug 1315716
[19:30] <brainwash> the upstream report is targeting xfdesktop and not thunar
[19:31] <elfy> then change one - obviously the same bug
[19:31] <brainwash> mmh, the ubuntu one does not mention "desktop" at all
[19:32] <brainwash> so I would assume that it is a general problem
[19:45] <elfy> certainly don't get a confirmation here
[19:49] <elfy> left a comment for them to read or ignore
[19:50] <elfy> if they confirm I'll sort the packages out on it - if they don't I'll ask them to check again ;)
[19:50] <brainwash> elfy: thanks