[01:36] <BCB> I've spent several hours tryingn to get a non-url to redirect/rewrite to a www url with not luck.  I've tried every iteration of apache2 rewrite/redirect rules on Ubuntu 22.04.1 LTS with no luch
[01:36] <BCB> luck
[01:36] <BCB> any suggestions.
[01:36] <wastrel> what's a non-url
[01:41] <BCB> wastrel(sorry) non-www URL
[01:41] <BCB> wastrel trying to redirect to a single URL
[01:43] <wastrel> idk gl
[01:43] <BCB> gl?
[01:46] <sarnold> 'good luck'
[01:57] <BCB> sarnold wastrel TY!
[01:58] <sarnold> :)
[03:05] <etudiant> hekll
[03:15] <Macwinner>  if I have a host machine with 12 cpu's, and i create 2 multipass instances and assign 12 cpu's to each, should this theoretically work?  would it just behave as if the combined processes within the instances were running directly on the host?
[05:56] <pizzaishere> hello anyone order a delivery
[05:56]  * pizzaishere is here
[07:29] <TheBigK> I am using the unofficial MS Teams app from the snap store by ismaelmartinez... and i have that running in startup ... which is fine in general.... but the problem is it will never update on its own because when its running snap refresh doesnt update the app. is there an easy way to check for updates before starting the app ? or should i just do a little bash script ...
[07:30] <TheBigK> the same problem is basically with every app... also for chromium for example... is there may be a way to update all snap apps before it starts the desktop?
[07:34]  * alkisg wishes operating systems would replace their shutdown button with a "download updates and shutdown" button (with the ability to avoid it up to 40 days) and be done with all the unattended upgrades for desktops...
[07:38] <Guest43> yeah that would be cool
[07:38] <Guest43> update and shutdown, windows 11 has that
[07:40] <TheBigK> i checked how snap is doing the refreshes
[07:40] <TheBigK> it does it 4 times a day.. but it will never update basically when the app is running 24/7
[07:41] <TheBigK> what a bullshit design
[07:41] <TheBigK> i might do a timer-service that does snap refresh at boot or something
[07:41] <TheBigK> the default behaviour is just stupid
[07:42] <TheBigK> im not happy with snap apps anyways... the performance sucks and quality of the programms often suck...
[07:43] <TheBigK> when i find time.. i might try debian again... i had some driver problem ... and the updates are also slowly backported... it was faster even on debian stable...
[07:50] <xmz> Excuse me, I would like to ask for help.
[07:50] <Guest43> yes
[07:50] <xmz> The ubuntu-22.04-preinstalled-server-riscv64+unmatched.img started with qemu, the kernel version is Linux 5.15.0-1018-generic. I compiled and installed a new kernel, but the new kernel cannot be started. It seems that u-boot needs to be set up.
[07:50] <xmz> I posted the qemu boot script and boot info here: https://dpaste.com/EKCHULY93
[08:54] <alunoepad062> oi
[08:54] <japanesegirl3> oie vey!
[08:54] <alunoepad062> hello support
[08:54] <japanesegirl3> hi yes
[08:54] <japanesegirl3> This is Ubuntu tech support
[08:54] <japanesegirl3> how can I help you
[08:54] <alunoepad062> i dont know any commands
[08:54] <alunoepad062> terminal commands
[08:55] <alunoepad062> can you help me get some?
[09:02] <alunoepad062> hi
[09:04] <japanesegirl3> i reccomended xnz repost question dont b mad k
[09:05] <xmz> [15:50] <xmz> Excuse me, I would like to ask for help.
[09:05] <xmz> [15:50] <Guest43> yes
[09:05] <xmz> [15:50] <xmz> The ubuntu-22.04-preinstalled-server-riscv64+unmatched.img started with qemu, the kernel version is Linux 5.15.0-1018-generic. I compiled and installed a new kernel, but the new kernel cannot be started. It seems that u-boot needs to be set up.
[09:05] <xmz> [15:50] <xmz> I posted the qemu boot script and boot info here: https://dpaste.com/EKCHULY93
[09:05] <xmz> Thanks.
[09:08] <japanesegirl3> u should also ask in #linux-offtopic
[09:08] <japanesegirl3> linux
[09:08] <arraybolt3> japanesegirl3: This is the right channel. Please don't disrupt this channel.
[09:09] <arraybolt3> xmz: You *might* try asking your question in #ubuntu-server also.
[09:11] <xmz> OK, thanks. I'll ask.
[09:23] <vimart> Had to done reinstallation recently and wanted to install "geoiplookup" which I had earlier but now can't locate the package,
[09:23] <vimart>            │isn't it available anymore in a repo?sudo snap install geoip-lookusudo snap install geoip-looku
[09:23] <vimart> y
[09:24] <vimart> sorry for wrong paste
[09:24] <vimart> I've had to done reinstallation and can't find "geoiplookup" in repo, isn't available anymore>
[09:24] <vimart> ?
[09:37] <ravage> vimart, https://packages.ubuntu.com/jammy/geoip-bin
[09:49] <vimart> ravage: thx bro, I'll look it up
[09:49] <vimart> I've got a lot of work with that reinstallation
[10:20] <vinnland> For people who use a VM setup for a lot of the day to day work... how do you handle keyboard clashes. I use macOS and I have a very specific keybindings. Some of my keybindings are similar to my Ubuntu box. When I create a VM, I want to use the same keys but I cannot because they clash. Is there a way to make keys active only on the VM while its open?
[10:52] <guzzlefry> How do I migrate to snap's version of Firefox?
[10:57] <SteelRose> guzzlefry: apt remove firefox ; snap install firefox
[10:58] <SteelRose> guzzlefry: why do you prefer the snap version?
[11:01] <guzzlefry> SteelRose: apt version is a bit behind and there seems to be a significant performance bug
[11:02] <guzzlefry> apt-cache policy doesn't tell me the patch version, but: Installed: 105.0+build2-0ubuntu<IP_ADDRESS>
[11:02] <SteelRose> guzzlefry: tbh, I stopped using FF a long time ago in favor of Brave
[11:03] <guzzlefry> yeah, I might cave and do that. I just hate the idea of a world with a single browser engine. :P
[11:04] <SteelRose> guzzlefry: yep, I get that too...and moving away from FF was a hard decision... but it was needed, as FF doesn't work in some pages I need for work
[11:04] <guzzlefry> Does Brave have anything like Firefox Sync?
[11:10] <BCB> I recently updated to Ubuntu 22.04.1 LTS and am now facing a "file_put_contents: failed to open stream: Permission denied" error that I can not figure out.  Any suggestions.
[11:10] <BCB> I'm tried multiple owner and permission configurgations to no avail.  This set up worked fine before the upgrade.  Any thought.
[11:14] <guzzlefry> BCB: Sounds like a PHP error?
[11:47] <tomreyn> BCB: which PHP variant / SAPI are you using? apache + mod_php, some webserver + somecgi + fpmd, something else? did you inspect the web server logs near the timestamp where this permission error occurs? what is open_basedir set to? which user ID is the PHP process running as, and how did you tell? which directory path is it trying to write to, and what's the output of    ls -la   on this directory (on a !pastebin)
[11:55] <dabbler> What's the proper way to start kde manually? Like 'systemctl start gdm' starts gnome.
[11:56] <dabbler> I don't see any kdm, kde, or plasma mentions among the systemd services
[12:00] <Guest7613> I think kde uses SDDM
[12:06] <BCB> tomreyn I check EVERY permission BUT the folder it was writing to!  That did the trick.  Thank you.
[12:07] <SteelRose> guzzlefry: yes, it does
[12:12] <tomreyn> BCB: glad you worked it out.
[12:37] <fahim> How can I post in linux mint forum?
[12:38] <arraybolt3> fahim: No clue. I don't think this is probably the right channel for this. They should just let you sign up and then post stuff like most other forums, I would think.
[12:38] <luna> yeah
[12:40] <fahim> I;m sorry ! I'm new here
[12:40] <arraybolt3> No problem. If you get tired of Mint, install Lubuntu, Xubuntu, or another official Ubuntu flavor and then we'll be able to help with problems in-person. :)
[12:41] <fahim> Thank You So much!!
[12:41] <arraybolt3> (Not that you shouldn't use Mint, btw, I've used it, it's cool.)
[12:41] <fahim> Oh! Thanks again
[13:14] <leobuilt> Hello
[13:16] <BluesKaj> Hi all
[13:16] <leobuilt> hi !
[13:36] <leobuilt> Is anybody using a wayland server on Ubuntu 22.04 ?
[13:36] <Habbie> yes
[13:36] <leobuilt> Working fine ?
[13:36] <Habbie> yes - it was the default for the raspberry pi 4 image, works fine
[13:37] <leobuilt> Nice ! ty
[13:37] <Habbie> (i also use wayland on my amd64 laptop but it runs debian)
[14:06] <ogra> leobuilt, wayland is the default for everyone n 22.04 except for nvidia users
[14:19] <crux73> For the close sources drivers you mean?
[14:20] <crux73> cause i think it would be wayland to for Nouveau drivers, not sure tho.
[14:20] <ogra> i dont think it makes that distinction (IIRC it only checks if there is the HW)
[14:20] <ogra> but i'm not sure
[14:20] <crux73> Ok.
[14:20] <ogra> and after all it is just two clicks at the login screen t switch
[14:20] <ogra> *to
[14:34] <jello> hello, does Ubuntu do backports? specifically, how would I go about requesting that unixodbc 2.3.11-2 be backported from kinetic to jammy?
[14:35] <lotuspsychje> !backports | jello
[14:36] <bittin> 22.10 building going on?
[15:01] <bittin> https://ubuntu.com/blog/canonical-releases-ubuntu-22-10-kinetic-kudu
[15:33] <PeterM-Ubuntu> Where is the release party again?
[15:33] <ogra> #ubuntu-release-party indeed
[15:36] <PeterM-Ubuntu> thanks @ogra
[15:38] <genii> !isitout
[15:38] <genii> heh
[15:39] <Habbie> nice ;)
[15:39] <gordonjcp> yay
[15:39] <genii> Seems to need updating since this release is 22.10 LOL
[15:39] <ogra> which is far from being out yet
[15:39] <gordonjcp> let me update machine to six months ago
[15:50] <paul424> hello, hello I need a never version of libOIS : https://packages.ubuntu.com/search?suite=default&section=all&arch=any&keywords=libois&searchon=names then 1.3
[15:50] <paul424> that is 1.5 for my snapcraft package build
[15:50] <paul424> any ideas what I can do ?
[15:59] <murmel> paul424: you would probably need to package it yourself
[16:03] <jhutchins> I thought snap was the packaging step, wouldn't you just build it from source?
[16:05] <murmel> jhutchins: yes, but I would still call it packaging ;)
[16:06] <jhutchins> Building a snap from .deb packages seems redundantly silly.
[16:24] <ogra> jhutchins, totally not ... there is enough SW that has been deprecated in the archive ... snapping the deb from a release where the SW was still supported make it available on all releases
[16:24] <ogra> *makes
[16:25] <ogra> (and indeed that also works the other way around)
[16:25] <murmel> ogra: are snaps always this complex to build (when looking at your packageproxy)?
[16:26] <ogra> re-packing debs is done quite often to provide backports to old releases to provide old and dead stuff to new ones
[16:26]  * ogra looks at his packageproxy ... to reply to that
[16:28] <ogra> murmel, well, the snapcraft.yaml is relatively simple ... the whole stuff around it like the launcer script and config handling is really full of brainfarts of mine trying out weird ideas ... you wouldnt need all this anymore today
[16:29] <murmel> ahh, I am right now looking at snaps/snapcraft, and thought, eh I use/used packageproxy, so why not see how it's being built
[16:29] <murmel> and was quite astonished, how much was going on in the repo
[16:30] <murmel> ogra: was quite bumped that debian repos are not enabled by default ;) so I had to look up how to do that
[16:30] <ogra> lol, sorry
[16:31] <murmel> no problem :) but the way you wrote on your package description, I thought it would enable all *.deb distributions
[16:31] <ogra> i packaged it to scratch my own itch at a time when building ubuntu-core images a lot ... so i only cared about ubuntu archives ... happy to take a PR
[16:32] <murmel> ogra: yeah, give me a bit, still learning the ropes
[16:32] <ogra> no hurry
[16:32] <ogra> the snap itself could really need an verhaul but i have probably painted myself in a corner with the weird config handling
[16:32] <ogra> *overhaul
[16:32] <ogra> (it is really old)
[16:33] <murmel> ogra: yeah, I already wanted to repackage it anyway to learn the ropes, and I saw that you still use core, which afair is deprecated oO?
[16:33] <murmel> or at least it's discouraged
[16:35] <ogra> the latter
[16:35] <ogra> it is actually supported til 2026
[16:35]  * ogra notes we're slightly offtopic 🙂
[16:38] <nominal_value> hey all, this is more server related, but in 22.04, how can i change the IP address and have it stick?
[16:38] <nominal_value> should i be using netplan?
[16:40] <ogra> yes
[16:40] <ogra> the netplan.io page has examples
[16:40] <nominal_value> ok aha well i will try from there. For some reason i cant get it to stick
[16:40] <nominal_value> after a reboot
[16:41] <wastrel> idk
[16:41] <wastrel> bye gl
[16:47] <DumbLDoor> Hello all!
[16:48] <DumbLDoor> Is 22.10 release out?
[16:48] <ogra> not yet
[16:48] <luna> in some hours
[16:48] <ogra> but in its last stages ... a few hours to go until the mirrors have synced
[16:49] <DumbLDoor> Thank you @ogra!
[16:49] <luna> 18:46 < sil2100> Okay everyone, images are published, mirrors will be syncing - will take a while though, so uh, it's still not 'officially released'
[16:49] <luna> 18:47 < sil2100> This can take 1-2 hours from now
[16:49] <DumbLDoor> Thank you @luna!
[17:02] <nominal_value> wow ok the netplan yaml is VERY picky when it comes to indents and spacing.
[17:13] <ogra> nominal_value, yaml is ... thats not a netplan thing 😉
[17:14] <ogra> indentation sould only be done by spaces and always at an even number of these
[17:16] <nominal_value> hmm
[17:16] <nominal_value> well all the netplan info i am finding seems to think so
[17:17] <nominal_value> atm i am unable to remove the old ip. I have local connectivity, but despite having a GW assigned, i cannot comm out to the internet
[17:17] <nominal_value> lotta work just to set a static ip, yeesh
[17:25] <LuckyMan> Hi, will the 22.10 torrent come out as soon as the .iso is launched?
[17:27] <nominal_value> i have literally copied and altered the example config from netplan.io and netplan test/apply says it cant be loaded lol
[17:38] <johnfg> hi folks
[17:39] <johnfg> I'm running latest with all updates.  For some reason, after installing the latest, I'm no longer able to connect via Remote Desktop, vnc.
[17:40] <johnfg> I get a prompt for a password, but it immediately disconnects after seeming to take it.
[17:48] <guzzlefry> Magnet links don't seem to work with the Firefox snap version...
[17:58] <alkisg_web> !last
[17:59] <alkisg_web> Strange, currently #debian syncs with matrix, #ubuntu doesn't... weird bridge issues
[18:01] <johnfg> How would I run the Settings app remotely, i.e., through an ssh -x session?
[18:25] <jStefan> LuckyMan, usually yes
[18:44] <johnfg> Interesting, that other programs run over ssh -X, but when I run, gnome-control-center, it does nothing.
[18:50] <alkisg_web> johnfg, try with dbus-launch first, to get a dbus
[18:57] <butax42_> !Ook Introduction to DevOps with Chocolate LEGO and Scrum Game.pdf  ::INFO:: 8MB ::HASH:: 654bcd4b93c4f655
[18:58] <butax42_> !Ook Introduction to DevOps with Chocolate LEGO and Scrum Game.pdf  ::INFO:: 8MB ::HASH:: 654bcd4b93c4f655
[18:59] <butax42_> @search devops
[19:04] <luna> Ubuntu 22.10 is now listed on ubuntu.com
[19:08] <c_89> Hi, due to a crash I was forced to restart the pc by turning it off from the shutdown button, from that moment on when I shut down the operating system, the shutdown screen of the various systemd services appears, but the last service I see in the screen is always "systemd-rfkill" while before it was "reached target shutdown" ... etc. Therefore I
[19:08] <c_89> have reinstalled the systemd package from synaptics but I think I am doing something wrong
[19:09] <c_89> Do you have any advice?
[19:13] <jStefan> c_89, seems that services queries the state of various RF switches on the computer (Wifi, bluetooth, etc), does it say anything else? an ok or fail?
[19:17] <c_89> jStefan I run this command: https://bpa.st/EBHQ
[19:23]  * luna downloading 22.10 from ftp.acc.umu.se now
[19:25] <c_89> jStefan I had only one device in soft block, now I ran `sudo rfkill unblock all` do you think that may be the problem?
[19:27] <jStefan> c_89, i don't have much experience on rfkill, I'm just looking at my outputs and comparing to yours to see if there something different. Did you try to grep logs for rfkill ?
[19:28] <jStefan> Ubuntu 22.10 has been posted on the ubuntu mailing list
[19:28] <luna> https://releases.ubuntu.com/22.10/ubuntu-22.10-desktop-amd64.iso
[19:29] <c_89> jStefan let's see I try to restart the pc after running the command I mentioned before, see if anything changes ... see you later ....
[19:30] <jStefan> people should use a link that manages mirrors automatically
[20:00] <jfsimon1981> /msg nickserv identify jfsimon1981 charly00
[20:01] <arraybolt3> jfsimon1981: Wonder who's about to change their password...
[20:01] <oerheks> jfsimon1981, time to change password
[20:03] <sarnold> jfsimon1981: it'd be nice if you picked something a bit stronger, too :)
[20:06] <oerheks> i think 'jfsimon1981' is prettty strong
[20:09] <sarnold> :)
[20:10] <carbonfiber> Using the linux console (without any desktop environment). Then running "sudo nano FILENAME" opens an instance of nano where text-selection using shift+arrows does not work. Despite this working as non-root. Why is that? And how can I make text-selection using shift+arrows work as root?
[20:16] <sarnold> carbonfiber: hmm, the nano manpage mentions something about the terminal supporting it.. try env | grep TERM and sudo env | grep TERM and see what the results are; if they are different that is probably worth exploring; if they're the same, then this guess is unlikely to be right :)
[20:16] <EriC^^> carbonfiber: worth a shot, try sudo -i nano filename
[20:17] <carbonfiber> EriC^^: doesn't work.
[20:17] <EriC^^> or sudo -H nano filename
[20:17] <carbonfiber> also doesn't work.
[20:17] <sarnold> we really all should have been using sudo -e filename  for years but I just can't get the hang of that
[20:18] <EriC^^> carbonfiber: does sudo su -
[20:18] <EriC^^> then nano filename work?
[20:18] <carbonfiber> also tried setting the .nanorc file explicitly using the --rcfile option. and also checked that both root and the normal user have no .nanorc files in their home directories.
[20:19] <carbonfiber> worth noting that the text gets highlighted if i use meta+A, so it is not an issue with the console colors either.
[20:20] <carbonfiber> EriC^^: that did not work either.
[20:20] <EriC^^> did you try sarnold 's suggestion on comparing TERM?
[20:21] <carbonfiber> both say "TERM=linux"
[20:22] <carbonfiber> also worth noting that the text-selection using shift-arrow works as root using gnome-terminal. and it works as non-root in the linux console. it is only the combination of root and the linux console which makes it not work.
[20:34] <EriC^^> fwiw carbonfiber i get the same behavior, odd
[20:34] <carbonfiber> EriC^^: Thanks for reproducing it :) Now I am not the only one :O
[20:34] <EriC^^> :D
[20:38] <EriC^^> carbonfiber: i was able to reproduce another error, if you do "sudo -u <your user> -s" to get a new shell, and run "nano filename" it stops working for the user too
[20:39] <carbonfiber> EriC^^: thanks. That is interesting.
[20:41] <enigma9o7> When does the name for Ubuntu LL get announced?
[20:42] <EriC^^> carbonfiber: very odd, if you do "sudo login <your user>" to login again, it stops working too
[20:43] <n9nu> i must be one of the few who dont use sudo
[20:44] <n9nu> its: 'su -'for me
[20:44] <n9nu> old school
[20:45] <sarnold> EriC^^: maybe compare env and sudo env and try setting some of the missing ones in the new shell?
[20:45] <arraybolt3> enigma9o7: Grief. We just finished whopping ourselves to push Kinetic out and we're already pushing towards LL? :P I also want to know the new name ASAP.
[20:47] <EriC^^> sarnold: this is diff <(env) <(sudo env) https://termbin.com/x8bj
[20:47] <enigma9o7> leaping lizards and lazy llamas and lounging lemus, the anticipation has me on edge
[20:47] <enigma9o7> s/lemu/lemur/g
[20:47] <arraybolt3> I dunno, a lemu sounds cool.
[20:47] <arraybolt3> Why says the animal has to exist?
[20:48] <jStefan> Seems my old 4GB usb flash, I've used for Ubuntu releases until today, is no longer big enough :'(
[20:50] <sarnold> EriC^^: cripes, no idea ;( none of those really feel like they're remotely related :(
[20:50] <arraybolt3> jStefan: Possibly, the image is 3.8 GB this time.
[20:50] <n9nu> how bout  something tech sounding
[20:50] <enigma9o7> no kidding hte iso is over 4gb? if its over 4.3 it wont fit on regular dvd even
[20:50] <GSMarquis> Im sure you were tired of 6mb per sec anyway.
[20:50] <n9nu> unpack the iso, remove the crap ya dont need
[20:51] <n9nu> language files, servers, desktops, etc
[20:51] <GSMarquis> Like snaps
[20:51] <jStefan> it's a valid perspective
[20:51] <jfsimon1981> Whoops
[20:51] <jfsimon1981> yep posted the pwd my mistake
[20:51] <jStefan> jfsimon1981, indeed!
[20:52] <jStefan> jfsimon1981, good you noticed, time to make it a stronger one too
[20:52] <n9nu> oh dear
[20:52] <GSMarquis> We have all done that once in IRC
[20:52] <n9nu> just use: password
[20:52] <arraybolt3> Better yet, hunter2.
[20:53] <GSMarquis> need a harder password...like password123
[20:53] <n9nu> heh
[20:53] <jStefan> I know a file of commonly used passwords, you can just pick anyone of those. They must be common for a "good" reason? (NOT)
[20:53] <jfsimon1981> did you see it, did i paste to the irc again ?
[20:53] <jfsimon1981> Don't worry i build a good pwd gen
[20:53] <n9nu> ur ok
[20:54] <jfsimon1981> Example -> 6tDDYJ8WwpTfmRrv
[20:54] <n9nu> something u save as a txt file and copy / paste
[20:54] <jfsimon1981> Another one 3k8kE5dEvy3Evq5r
[20:54] <jStefan> jfsimon1981, there was a password posted on chat a while ago, don't know if it happened more than once.
[20:54] <jfsimon1981> Yep i changed it now
[20:55] <jStefan> yeah don't use those last two ;)
[20:55] <jfsimon1981> Thanks for notice
[20:55] <GSMarquis> You added a "1" ?
[20:55] <jfsimon1981> they're just unique ones not in use
[20:55] <jfsimon1981> I made it with a c++ tool, it gens a 15 chars
[20:55] <carbonfiber> EriC^^:  Don't think it is the environment variables since "sudo -E -u USERNAME -s" doesn't work either. And it preserves all the environment variables which can be verified by running "env" afterwards.
[20:55] <EriC^^> carbonfiber: i think im close
[20:55] <enigma9o7> dolphins is a good password
[20:55] <EriC^^> 1sec..
[20:55] <carbonfiber> EriC^^: that sounds interesting.
[20:55] <jStefan> jfsimon1981, i think you can choose to authenticate as part of your connection, instead of a msg
[20:56] <n9nu> yeah
[20:56] <n9nu> i have mine in the server/connection tab
[20:56] <jfsimon1981> yes
[20:57] <n9nu> anyone else using a PRIME or OPTIMUS lappy
[20:57] <n9nu> and have it setup to actually use it
[20:58] <jStefan> https://libera.chat/guides/sasl
[20:59] <jfsimon1981> thanks
[21:00] <EriC^^> carbonfiber: aha interesting
[21:00] <EriC^^> no dice here
[21:01] <carbonfiber> :O
[21:01] <EriC^^> something to do with sudo for sure, i tried to login to root and it worked in the tty
[21:01] <arraybolt3> carbonfiber: Can you restate what was happening? Sudo problems sounds familiar to me.
[21:01] <arraybolt3> You might just need to update your system.
[21:01] <EriC^^> then tried sudo env and sudo env in tty vs display to see why does it work in the gui, no dice
[21:01] <carbonfiber> maybe sudo changes something which isn't an environment variable? such as some tty properties or something.
[21:03] <EriC^^> hmm, bingo carbonfiber !
[21:03] <arraybolt3> carbonfiber: I see it. You may be running into a CVE fix in sudo that does weird stuff with pseudoterminals. Try updating your system, the latest version of sudo in Ubuntu should revert that fix and make things work right again.
[21:03] <EriC^^> i did sudo visudo, and put a comment before #Defaults       use_pty and now it works with sudo nano filename in tty
[21:03] <EriC^^> carbonfiber: ^
[21:03] <arraybolt3> EriC^^: Yeah, that's the mess the update should undo.
[21:04] <carbonfiber> arraybolt3: do you have any reference to the specific bug ID or something?
[21:04] <arraybolt3> I do, let me dig it up.
[21:05] <n9nu> wow. 1TB download for WarThunder 4 Linux
[21:05] <arraybolt3> Looks unrelated, but this is the bug, I'm sure of it. https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-settings/+bug/1965439
[21:05] <n9nu> sweet
[21:05] -ubottu:#ubuntu- Launchpad bug 1965439 in kubuntu-settings (Ubuntu Jammy) "[SRU] kdesu fails to authenticate with sudo from Jammy" [High, In Progress]
[21:05] <arraybolt3> Ouch, the fix actually hasn't been fully released yet.
[21:05] <arraybolt3> It's still in the -proposed archive (don't enable that, there be dragons).
[21:06] <arraybolt3> OK, just comment out that one line like EriC^^ was suggesting.
[21:06] <carbonfiber> arraybolt3: thanks for the link.
[21:08] <carbonfiber> EriC^^: thanks for finding the fix.
[21:08] <carbonfiber> But I am not sure I entirely understand what the problem was.
[21:08] <carbonfiber> beside sudo doing some wierd tty stuff.
[21:09] <EriC^^> carbonfiber: really it was your comment about sudo changing something other than an env var, same here
[21:12] <arraybolt3> nhaines: Hey, if you're around, can you check your Reddit modmail? I just posted an official announcement related to Lubuntu on Reddit and don't have my Ubuntu Member flair yet. Would be awesome if that could happen very soon so that the post looks official.
[21:13] <arraybolt3> (I have my Reddit username on my Launchpad account.)
[21:14] <sarnold> carbonfiber: the sudo security fix is to prevent a program from shoving characters onto the terminal's input queue of whoever ran sudo; it's not a big deal when using a user account to elevate to root, since the program running as root can just run as root :) but it's a big deal for changing to other users, or worse yet, going from root down to a user
[21:33] <carbonfiber> sarnold: hmm ok thanks.
[21:35] <carbonfiber> But I still don't understand why nano then works partially. I would understand if the command ran with sudo could not output anything at all. But I don't understand why it is only selection using shift+arrows that doesnt work.
[21:35] <carbonfiber> :S
[21:35] <sarnold> carbonfiber: same here
[21:36] <sarnold> carbonfiber: if you can find an answer to that I'd be very curious to hear the answer :)
[21:36] <carbonfiber> :)
[21:45] <litheum> i'm using 22.04.1 LTS right now, and the email announcement for 22.10 makes it sound like i should be able to upgrade my installation today. however neither the GUI "Software Updater" program nor do-release-upgrade show a new release. anything i should do, or should i just wait a few days?
[21:45] <sarnold> litheum: first, are you *sure* you want to upgrade? an lts is a pretty good place to sit..
[21:46] <bob_x1> how can i blacvklist modules for booting ? i added lines blacklist mod_name into /etc/modules but they are still loaded during boot
[21:47] <litheum> sarnold: yes, this is a goofy laptop that i don't do anything important with
[21:47] <sarnold> litheum: I'm not sure when exactly it'll happen, but sooner or later the new release will be added to https://changelogs.ubuntu.com/meta-release and then the upgrader will be able to upgrade to it easily; until then, you can use do-release-upgrade -d
[21:47] <sarnold> litheum: sweet :D thanks
[21:47] <genii> sarnold: Besides which I think default in etc/update-manager/release-upgrades is LTS
[21:47] <sarnold> genii: oh right, I always forget that thing
[21:48] <genii> ( when you're already on an LTS )
[21:49] <litheum> genii: yeah, i updated that in the GUI config, and it looks like it's persisted correctly to that file
[21:52] <litheum> it seems so weird that these emails announcing the new release are out but https://changelogs.ubuntu.com/meta-release is not updated
[21:56] <sarnold> litheum: aha check out
[21:56] <sarnold> litheum: check *now* rather
[21:56] <sarnold> my god my fingers are getting stupider every day
[21:58] <litheum> sarnold: hah, great timing! thank you :-)
[21:59] <sarnold> litheum: it weren't me, I'm just connecting the dots, hehe
[22:10] <nhaines> arraybolt3: done!  :)
[22:11] <arraybolt3> nhaines: Thank you so much!
[22:11] <nhaines> arraybolt3: no problem.  Thank you for your contributions to the Ubuntu community.  :)
[22:12] <arraybolt3> nhaines: Is it possible it will take a bit to show up? I'm not seeing it on my end.
[22:12] <nhaines> Might take a minute or two.  Reddit caches in mysterious ways.
[22:13] <nhaines> It's showing up for me on old reddit.
[22:13] <arraybolt3> :+1: Thank you!
[22:18] <PeterM-Ubuntu> thank you and congratulations to the release and web team
[22:18] <PeterM-Ubuntu> well don
[22:18] <PeterM-Ubuntu> e
[22:34] <ItsFriday> @bansearch
[22:35] <ItsFriday> @bansearch ItsFriday
[22:48] <Aavar> On one of my machines I can see everytime it boots that something fails. How can I figure out what it is?
[22:49] <murmel> Aavar: /var/log/syslog can show you something, or journalctl -b 0
[22:57] <Aavar> murmel: thank you
[23:03] <jhutchins> Servers need to be nimble and flit from network to network.
[23:03] <jStefan> n9nu, I think I've managed to make the iso fit into my 4GB usb by excluding the 390 version of the nvidia drivers. Those drivers are from the geforce 400 series era, so I'm not worried.
[23:03] <n9nu> there ya go....good deal
[23:03] <jhutchins> jStefan: Is that the non-free driver image/
[23:03] <jhutchins> ?
[23:04] <n9nu> i always dump the other xservers as well - just me
[23:04] <jStefan> jhutchins, yes, I believe so, and I can always install without the nvidia drivers, and get them later, I suppose.
[23:05] <jStefan> I kept all the other nvidia drivers, i just needed to strip the 390's, that should give me the space I needed
[23:05] <n9nu> it will install that nouveau crap by default
[23:06] <n9nu> which is fine actually for most
[23:06] <n9nu> i just prefer the oem
[23:06] <jStefan> yeah, but it should boot and allow me to download once installed, in the hypothetical case that I do use a 400 series nvidia card
[23:07] <n9nu> yeah..i should realize ur using ubuntu
[23:07] <n9nu> im on debian....i come in here often though
[23:08] <jStefan> aren't the debian installers usually smaller ?
[23:08] <n9nu> actually i honestly don't know.
[23:08] <n9nu> the install .iso is just under 4GB
[23:09] <n9nu> however i use the rolling release like....Sid
[23:09] <n9nu> i just update each night
[23:13] <jStefan> seems the debian dvd image is 3.6GB, but i had to dig a little to find it, seems netinst image is more common? and that's around 400 MB
[23:14] <carbonfiber> EriC^^ , arraybolt3 , sarnold : I found out what the issue was in more detail. It is actually rather simple when you know it. A pty master running in the linux console does not send the shift key as a standalone key to the pty slave, rather it sends the combined key. So "shift+a" does not send "shift+a" to the pty slave, it sends an "A". But it does not send shift together with the arrow keys. So nano running at the pty slave
[23:14] <carbonfiber> never receives the shift key.
[23:14] <carbonfiber> Running an ssh client from the linux console, have similar behavior. It also makes it so that text-selection using shift+arrow keys doesnt work. sudo with "use_pty" just works kinda similar to ssh.
[23:15] <n9nu> yeah...i have a 2.5Gbit FTTH here so i use the net install
[23:17] <sarnold> carbonfiber: *beautiful*! :D Thanks so much for reporting back!
[23:18] <carbonfiber> np :)
[23:38] <enigma9o7> jstefan: the netinst asks you which desktop you want and downloads it.   unlike ubuntu which is only gnome, or a different iso if you want a different desktop.
[23:39] <n9nu> plasma rules
[23:39] <jStefan> enigma9o7, I'm just stubborn and sticking to a 4GB usb for too long :) ... and I'm still finding ways to stick with it
[23:40] <enigma9o7> I was annoyed when distros stopped fitting on a CD.
[23:40] <enigma9o7> But if they stop fitting on a DVD I'll be even more annoyed.
[23:41] <jStefan> I just don't want to use a brand new 32GB (or more) to fit a 4.01 GB image on it. Seems like a waste?
[23:50] <jStefan> why does ubuntu not enable fast_commits upon creation of ext3 fs's. Are fast commits not ready for prime time?
[23:50] <jStefan> ext4*
[23:55] <matsaman> jStefan: probably the same reason anything doesn't enable anything new immediately
[23:55] <jStefan> it was made available on kernel 5.10
[23:56] <sarnold> jStefan: it's probably worth a bug report to ask for the default to be flipped
[23:56] <sarnold> jStefan: it might help to know if a filesystem written with the feature enabled can be properly consumed by earlier kernels


[16:59] <lool> Do we have a meeting?
[17:00] <ogra> wouldnt that be 1h late already ?
[17:00] <lool> No
[17:00] <lool> Uh why did it move
[17:00] <ogra> move ?
[17:01] <lool> For some reason I just got the google reminder
[17:01] <ogra> heh
[17:01] <ogra> doesnt look like there is one today though
[17:03] <ScottK> There's three of us here, so feel free to take credit for a meeting on your status report if you want.
[17:03] <ScottK> ;-)
[17:04] <lool> :)
[17:32] <lool> ogra: Did your OTG port work on the beagle?
[17:33] <ogra> never tried it ....


 ubuntu still has a blue tick :P
[18:37] <valorie> ...
[18:38] <valorie> amazing that the company of a millionaire is treated better than a foss project


[09:50] <slickymaster> good morning all
[09:51] <ochosi> morning
[09:52] <slickymaster> morning ochosi. Good to have you here because I noticed that there's a correction that has to be made to the formatting of http://docs.xfce.org/apps/parole/usage
[09:53] <slickymaster> ochosi: right now the audio section isn't formatted as a title, it's in the continuation of the last paragraph of the DVD section
[09:53] <ochosi> brainwash: i know that currently the screen gets blanked twice, it even gets blanked twice on every display. kinda busy atm so i don't know when i'll really get to looking at the background-setting you mentioned ...
[09:55] <ochosi> slickymaster: thanks, good catch! fixed
[09:55] <slickymaster> ochosi: ^^^^
[09:55] <slickymaster> ochosi: np
[09:55] <slickymaster> knome: ping
[09:56] <ochosi> slickymaster: i just realised now, but we'll have to add a "playback" section to the keyboard shortcuts
[09:57] <ochosi> "Right arrow" > skip ahead 10secs
[09:57] <ochosi> etc
[09:58] <slickymaster> ochosi: you mean another table named playback to that section?
[09:58] <ochosi> yeah, i'm currently working on it
[09:58] <ochosi> thought i'd just quickly chuck it in, it's rather easy to do
[09:58] <slickymaster> ochosi, if you feel like there's already plenty in your hands to deal with, I'll be glad to do it for you
[10:00] <ochosi> slickymaster: actually, yeah, if you can/want... :)
[10:01] <ochosi> i'll have to link you to the section of parole's code though that explains that
[10:01] <slickymaster> ochosi: No worries, I'll do it
[10:01] <slickymaster>  I would appreciate the link
[10:03] <ochosi> they start here: http://git.xfce.org/apps/parole/tree/src/parole-player.c#n2441
[10:04] <ochosi> and: seek_short = 10, seek_medium = 60, seek_long = 600
[10:04] <ochosi> (seconds)
[10:04] <ochosi> as you can see there are more shortcuts that aren't in the docs right now
[10:04] <ochosi> (f for fullscreen)
[10:04] <ochosi> (p for playpause)
[10:05] <slickymaster> ochosi: I'll add those to the already existing tables
[10:07] <slickymaster> ochosi: I'll need just another thing though, the link to bluesabre's dokuwiki. I've lost it :(
[10:09] <ochosi> hehe, no worries
[10:10] <ochosi> slickymaster: http://smdavis.us/doku/doku.php?id=usage&#keyboard_shortcuts
[10:11] <slickymaster> ochosi: thks
[11:30] <brainwash> ochosi: mmh, simply move the first set_background call and use it as fallback if there is no user background set via accountsservice?
[11:31] <brainwash> ochosi: well, currently I simply commented the first call :D
[11:31] <brainwash> out
[11:32] <brainwash> but you will have to fix this, because it does cause the strange unblank behavior on two different systems
[11:33] <brainwash> bug report required?
[11:40] <brainwash> looks familiar -> http://ubuntuforums.org/showthread.php?t=2188790
[11:55] <knome> slickymaster, pong
[11:56] <slickymaster> knome, good morning
[11:56] <knome> g'day
[11:56] <ochosi> brainwash: ok, i'll try to check it a bit later today then ;)
[11:57] <slickymaster> so I've speak with balloons regarding https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/1251332 and his opinion is that he should go with
[11:57] <slickymaster> sudo -i to get to a root prompt and there launch whatever graphical application
[11:58] <slickymaster> knome: so, if there's no objections from you I'll go ahead with that to re-write the documentation
[11:58] <knome> slickymaster, ok
[11:59] <slickymaster> knome: I'll do it then and later on I'll propose a merge
[12:04] <knome> slickymaster, ok, thanks
[12:06] <slickymaster> knome: np
[12:57] <ochosi> brainwash: wanna show me the patch that worked for you?
[13:24] <brainwash> ochosi: there is none yet, I simply commented out the first set_background call
[13:24] <ochosi> that one was actually added to help with nouveau drivers when setting the background...
[13:24] <brainwash> that's obviously not the best solution
[13:25] <ochosi> it's a bit of a tricky situation, not everything seems to work with all drivers
[13:25] <brainwash> I mean the part in the main function
[13:25] <brainwash> to set the background which is specified in the config file
[13:26] <ochosi> which is why i'm a bit hesitant to touch this stuff, i only have one laptop to test things on
[13:27] <brainwash> well, create an extra branch :)
[13:27] <brainwash> I can test it
[13:28] <ochosi> hmpf yeah, all rather time-consuming and much tapping in the dark
[13:34] <ali1234> what's this bug about backgrounds?
[13:38] <ochosi> ali1234: well it's an issue in lightdm-gtk-greeter
[13:38] <ali1234> lightdm always faded nicely from the default background to the user specified one for me
[13:38] <ali1234> i thought it was supposed to do that
[13:38] <ochosi> what greeter are you using?
[13:38] <ochosi> i guess unity-greeter, right?
[13:38] <ali1234> yeah
[13:38] <ochosi> (lightdm-gtk-greeter doesn't fade)
[13:38] <ali1234> what's the difference?
[13:39] <ali1234> i thought unity used lightdm
[13:41] <ochosi> lightdm is the display server
[13:41] <ochosi> the rest are greeters
[13:41] <ali1234> so the greeter is like a modular component?
[13:41] <ochosi> yeah
[13:41] <ali1234> ok, got it
[13:41] <ochosi> the visual component
[13:41] <ochosi> so the lightdm-gtk-greeter was written by ligthdm's author as a reference greeter
[13:41] <ali1234> so who else uses the gtk one?
[13:42] <ochosi> bluesabre and me picked it up and started improving it bit by bit
[13:42] <ochosi> lubuntu i think
[13:42] <ochosi> and maybe even distros outside ubuntu
[13:42] <ochosi> (i think lunar linux, not sure anymore)
[13:43] <ali1234> any reason why we don't use unity-greeter?
[13:43] <ali1234> it's pretty nice...
[13:43] <ochosi> well, firstly it depends on indicators
[13:44] <ochosi> which we couldn't use for ages now
[13:44] <ochosi> basically since they were ported to gtk3
[13:44] <knome> i think -gtk-greeter fits better with our style anyway, at least now that we've worked with it
[13:45] <ochosi> the other thing is that the gtk-greeter is a component we control, so we can also introduce changes that make sense for xubuntu
[13:45] <ochosi> e.g. introducing screen-blanking in case it's used as a lockscreen would be somewhat harder to get into unity-greeter
[13:45] <ali1234> random: if the greeter can read the user's background, can it also read their theme?
[13:46] <ochosi> it can read whatever accountsservice allows
[13:47] <ali1234> accountsservice documentation isn't online except in source form
[13:47] <ochosi> yeah, it's indeed not very well documented (it's been a while since i dealt with it)
[13:48] <ali1234> and the package doesn't include the built docs
[13:48] <ochosi> oh, and the user-wallpaper isn't in accountsservice upstream
[13:48] <ali1234> so pretty much no chance then
[13:48] <ochosi> that's an ubuntu-specific patch that never made it upstream (for whatever reason
[13:48] <ochosi> )
[13:49] <ali1234> so anyway... if we can't fix the double background bug, how about implementing the fade/transition instead?
[13:50] <brainwash> why can't we fix it? o.o
[13:50] <ali1234> well, it sounds like the code is a bit fragile with all different drivers
[13:55] <brainwash> so we should disable the accountsservice part?
[13:57] <ochosi> i'm not sure why we should disable the accountsservice part
[13:57] <ochosi> it's not fragile at all
[13:57] <ali1234> fix it then :)
[13:57] <ochosi> yeah, i said i'll try to do so once i have more time
[13:57] <ochosi> and testing resources are quite limited for me also
[13:58] <ochosi> i already added a patch recently that should improve things, but it seems it doesn't work for everybody
[13:58] <brainwash> I can write a patch (the way I like it to be fixed)
[13:58] <ochosi> sure, go ahead
[13:58] <ochosi> we can do it in a branch and try to get some testing
[13:58] <ochosi> i'm all for fixing things
[13:59] <ochosi> ali1234: fwiw, transitions and fades tend to produce lots of code. be my guest if you wanna submit a patch ;) (you could even use parts of thunar-desktop i guess)
[14:01] <ali1234> is this thing really only 2000 lines of C code?
[14:02] <ochosi> hehe
[14:02] <ochosi> well personally i think if we wanna do fancy stuff like that, we should switch to the html engine
[14:03] <ochosi> or even just fork unity-greeter and make it behave/look the way we want...
[14:03] <ali1234> so every time you change the user selection it changes the background too
[14:04] <ochosi> yup
[14:05] <ali1234> making it do a fade would probably add like 5 lines of code
[14:06] <ochosi> i'm totally happy to test and merge patches ;)
[14:08] <ali1234> i am confused what this is supposed to achieve: http://bazaar.launchpad.net/~lightdm-gtk-greeter-team/lightdm-gtk-greeter/trunk/view/head:/src/lightdm-gtk-greeter.c#L1310
[14:10] <ochosi> what do you mean specifically?
[14:10] <ali1234> the if(!matched) part
[14:10] <ochosi> (just as a note in advance: as i mentioned before, we're not the authors of the greeter, we're just maintaining it as it was dropped by robert_ancell a longer while ago)
[14:10] <ali1234> if you type a wrong username, it uses the first user's background?
[14:11] <ochosi> well
[14:11] <ochosi> the thing is: in xubuntu we use the user-list (in e.g. debian they don't they use the user-entry)
[14:12] <ochosi> with the user-list, you could only type a wrong username when using "other"
[14:12] <ochosi> as a few of the last patches by our debian maintainer have shown, we didn't really take care of the user-entry enough
[14:12] <ali1234> actually, i understand it
[14:12] <ochosi> oh, ok
[14:12] <ali1234> it's the initially selected user
[14:14] <ali1234> what if there are no users though?
[14:15] <ali1234> something to test: install in a vm, usermod your UID to <1000, see if greeter crashes
[14:19] <ali1234> is there some kind of testing harness for this?
[14:20] <ali1234> "lightdm --test-mode --debug" apparently
[14:21] <ali1234> indeed, it shows the bug
[14:23] <ochosi> hm
[14:25] <ali1234> so where do you maintain it if upstream dropped it?
[14:25] <ochosi> in the same place, bzr
[14:25] <ochosi> (i meant launchpad)
[14:25] <ali1234> ok
[14:26] <ochosi> lp:lightdm-gtk-greeter
[14:31] <ali1234> what do all the files in /etc/lightdm/*.conf do?
[14:34] <ochosi> you can use them to select the greeter / configure lightdm / configure the greeter/s
[14:34] <ali1234> so how do i make it load ~/Source/lightdm-gtk-greeter/src/lightdm-gtk-greeter
[14:34] <ochosi> so e.g. in /etc/lightdm/lightdm.conf you can select the greeter
[14:35] <ochosi> did you install the greeter?
[14:35] <ochosi> or what setting do you want to change specifically?
[14:35] <ali1234> i want to use the greeter i just built without installing it
[14:36] <ali1234> ah... it needs a .desktop file specially named
[14:38] <ali1234> hmm that's interesting
[14:39] <ali1234> it looks very different with default settings
[14:39] <ochosi> yeah
[14:39] <ochosi> it does
[14:39] <ochosi> lack of icon-theme, gtk-theme etc are the usual issues
[14:40] <ochosi> i considered providing a good fallback gtk-theme
[14:40] <ali1234> it looks ok
[14:40] <ochosi> yeah, could be better though
[14:40] <ali1234> just different
[14:40] <ochosi> and also some fallback icons, to be sure
[14:40] <ochosi> otoh so far no-one has complained about it ;)
[14:41] <ali1234> to be honest i think i prefer the defaults to the way xubuntu configures it
[14:45] <ochosi> fine by me
[14:45] <ochosi> we considered letting greeter-themes even change the UI file
[14:46] <ochosi> in general, it wouldn't be hard to ship multiple configuration files and let the user choose
[14:46] <ali1234> so why does it look different even after make install?
[14:47] <ochosi> because the xubuntu config file isn't in the bzr repo
[14:47] <ali1234> but it is still in my filesystem
[14:47] <ochosi> not sure i get it
[14:47] <ochosi> if you install the greeter, it overwrites the lightdm-gtk-greeter.conf file
[14:48] <ochosi> as in: the one that was shipped with xubuntu-default-settings
[14:48] <ali1234> it didn't
[14:48] <ochosi> then you didn't add prefix=/usr maybe?
[14:48] <ali1234> /etc/lightdm/lightdm-gtk-greeter.conf is unchanged
[14:48] <ochosi> maybe wrong prefix, it should change that file
[14:49] <ali1234> oh i see
[14:49] <ali1234> so it's really reading the config from somewhere completely different because i built it with the wrong prefix
[14:50] <ochosi> yeah, i'd say so
[14:50] <ali1234> yeah, fixed
[14:51] <ochosi> good
[17:11] <skellat> I'm going to have to look at LP Bug 1252800 later today
[17:12] <knome> skellat, new doc package isn't uploaded to trusty yet.
[17:18] <slickymaster> knome: I'm not 100% sure, but apparently no
[17:54] <ali1234> ok, so what exactly is so terrible about simply not making the first call to draw the background?
[17:55] <ali1234> if it fixes some driver bug, what about if we draw a black background here instead
[17:55] <ali1234> and then draw the user or default background later
[17:56] <ochosi> tbh i think the call didn't really help with nouveau
[17:56] <ochosi> so i think we can also look into restructuring that
[17:57] <ali1234> i can't see a reason why just skipping that draw will hurt anything
[17:57] <ali1234> but drivers are weird so who knows
[17:57] <ochosi> yeah, they are...
[17:57] <ochosi> well i'd suggest we work in a branch and then do testing with all drivers we can
[18:00] <ochosi> it's important though to keep in mind that the greeter shall not fail
[18:00] <ochosi> it's too important
[18:01] <ali1234> well the easiest way to guarantee that is to not functionally change it
[18:01] <ali1234> ie by drawing a black pixmap on that first call, and only the first call
[18:01] <ochosi> which is what bluesabre and me have done mostly
[18:04] <ochosi> i can also imagine doing functional changes, as long as there's someone at work who feels confident with that (i don't)
[18:09] <ali1234> @2000 lines of code there's a limit to how many bugs there can possibly be
[18:09] <meetingology> ali1234: Error: "2000" is not a valid command.
[18:09] <ochosi> indeed
[18:10] <ochosi> depending though on what kind of other stuff you involve
[18:10] <ochosi> many of our bugs have been lightdm bugs
[20:03] <elfy> hi sergiobenrocha2
[20:03] <elfy> knome: sergiobenrocha2 is looking to get more involved with us :)
[20:03] <knome> hey sergiobenrocha2
[20:03] <elfy> I've been moving him about freenode ... we've come here now
[20:04] <knome> welcome
[20:04] <Unit193> Hah.
[20:04] <Unit193> Welcome to another channel!
[20:04] <elfy> quick line from another channel - which sums it up
[20:04] <knome> why didn't i get that tour?
 elfy: ok, is possible that I create an wishlist in launchpad, and appears in this page, if the feature is good?
[20:04] <elfy> knome: please join #ubuntu+1
[20:05] <elfy> then when you've done that - can you come here :p
[20:06] <knome> lol
[20:06] <sergiobenrocha2> thanks everyone
[20:06] <knome> done
[20:06] <elfy> :)
[20:06] <knome> *that* was all of freenode?
[20:07] <elfy> no - just the bits I dragged sergiobenrocha2 around to
[20:07] <elfy> he started in #xubuntu
[20:09] <knome> sergiobenrocha2, we basically just finished creating roadmap
[20:09] <knome> sergiobenrocha2, was there something specific you had in your mind for the wishlist?
[20:09] <sergiobenrocha2> humm, yes, a thing or 2... or more
[20:10] <sergiobenrocha2> to make xubuntu more friendly
[20:10] <knome> would you like to share them with us here or want to keep secrets?
[20:10] <elfy> :)
[20:10] <sergiobenrocha2> haha
[20:11] <sergiobenrocha2> so:
[20:14] <sergiobenrocha2> 1 - create launchers in panel would be more friendly in right-click, it is better to pop-up a configuration window that create a complete launcher, and not only an empty gray icon
[20:14] <knome> sergiobenrocha2, did you know you can drag-and-drop launchers from the menu to the panl?
[20:14] <knome> *panel too
[20:14] <sergiobenrocha2> sorry for english... portuguese is my language
[20:14] <Unit193> Translator standing there ^ ;)
[20:15] <sergiobenrocha2> knome: but it possible to drag-and-drop from whiskermenu? I'm using it
[20:15]  * knome shrugs
[20:15] <knome> i don't use a menu at all, so i don't know
[20:16] <knome> maybe somebody who uses whiskermenu knows
[20:16] <knome> possibly
[20:16] <knome> maybe you should try. :)
[20:17] <sergiobenrocha2> I can drag-and-drop only favorites apps from whiskermenu, like terminal and thunar. Others, in sub-categories, it not possible
[20:17] <knome> you should file a wishlist bug against whiskermenu for that
[20:17] <knome> because it works with the regular xfce menu
[20:18] <sergiobenrocha2> ok
[20:18] <sergiobenrocha2> but whiskermenu is from ppa, how can ubuntu-bug will report that?
[20:19] <knome> i don't think it can... you have to report manually
[20:19] <elfy> do it manually - if you can
[20:19] <knome> https://github.com/gottcode/xfce4-whiskermenu-plugin/issues?labels=bug&state=open
[20:19] <knome> file a new issue.
[20:20] <sergiobenrocha2> humm, ok
[20:20] <knome> probably tag it with "feature"
[20:24] <ali1234> ochosi: as usual, when i start looking closely at some code, i start to notice it's kinda funky
[20:25] <ali1234> i have a feeling this thing leaks a display-sized xlib surface every time it changes the background
[20:25] <ali1234> the set_background code also does a bunch of surface setup, before which things may not work properly
[20:32] <sergiobenrocha2> I created the issue
[20:33] <sergiobenrocha2> but I can not see, if i click in "Issues" tab
[20:33] <sergiobenrocha2> it's the number 37
[20:34] <sergiobenrocha2> oh, ok, not worry
[20:40] <ali1234> confirmed, lightdm-gtk-greeter leaks memory like crazy.
[20:43] <brainwash> ali1234: surprise? :)
[20:43] <ali1234> never :(
[20:43] <brainwash> so you plan to fix the background part?
[20:43] <ali1234> i'm not sure i want to touch this code
[20:44] <ali1234> all this background stuff is related
[20:44] <ali1234> the only easy fix is to replace that first sat_background() with something like clear_background() which will just clear it to black but otherwise do the exact same as set_background
[20:45] <ali1234> ie all the memory leaking and stuff
[20:45] <ali1234> the alternative is to rewrite it so that allocation and drawing are separate
[20:45] <ali1234> this would fix both problems
[20:45] <ali1234> but it's a quite big refactoring
[20:46] <brainwash> allocation of the background image?
[20:46] <ali1234> and i'm not sure if i really care for something i see for 10 seconds twice a month
[20:46] <ali1234> so, when the greeter starts up it makes a pixmap which is the background
[20:46] <ali1234> actually, set_background() does this
[20:47] <ali1234> it creates a xlib pixmap, then draws the background into it with cairo
[20:47] <ali1234> but the problem is that the next time you call it, it makes another new pixmap and does not free the old one
[20:47] <brainwash> yes, but the greeter does it twice, if accountsservice provides an user background
[20:47] <sergiobenrocha2> I accidentally created a duplicate, but I changed it to an another issue, it is Issue #37. Can someone take the duplicate label?
[20:47] <ali1234> yes, it does it every time you select a different user from the list
[20:48] <brainwash> right
[20:48] <ali1234> if you sit and click different users you can make it leak hundreds of mb if you are patient
[20:48] <brainwash> no one does that
[20:48] <knome> ali1234, we would be grateful if you fixed that
[20:49] <ali1234> brainwash: could be a security vuln, i dunno...
[20:49] <ali1234> who knows what happens if the display is locked and you crash lightdm...
[20:49] <ali1234> anyway the thing is, it has to allocate and leave allocated that pixmap
[20:49] <ali1234> it might even be necessary that the pixmap exists before you start doing gtk stuff
[20:50] <brainwash> the background won't change if the screen is locked via greeter
[20:50] <ali1234> this might be the nouveau bug that was mentioned
[20:50] <ali1234> so this means you can't just defer drawing the background, because it also *creates* the background
[20:51] <brainwash> I simply want this bug to be fixed -> bug 1251431
[20:51] <brainwash> this also fixes the light-locker issue for me
[20:51] <ali1234> what does?
[20:52] <brainwash> ochosi made a change, so that light-locker blanks the screen after locking it
[20:52] <brainwash> it only works for me, if the background is set only once
[20:53] <ali1234> right yeah, that makes sense
[20:53] <ali1234> you know what i said about those pixmaps getting leaked?
[20:53] <brainwash> uhm, it's bad
[20:53] <ali1234> well, i bet the patch he made expects there to be only one
[20:53] <ali1234> so it hides the top one
[20:53] <ali1234> but there's still a stack of leaked ones behind it
[20:53] <ali1234> so to fix *that*
[20:54] <ali1234> requires the "proper" (but harder) fix of refactoring this thing
[20:54] <brainwash> I mean this here "XForceScreenSaver(display,ScreenSaverActive);"
[20:55] <brainwash> called twice unblanks the screen
[20:56] <brainwash> at least for me
[20:56] <brainwash> on two different systems
[20:56] <ali1234> yeah
[20:56] <brainwash> not this particular line, but the code part
[20:56] <ali1234> hmm
[20:56] <ali1234> no sure what you mean really
[20:56] <brainwash> the communication with X
[20:57] <ali1234> the thing is that all those leaked background pixmaps persist after the greeter exits
[20:57] <brainwash> yes, but that's not related to the blanking issue :)
[20:57] <ali1234> well, why did you mention it then?
[20:58] <brainwash> it's related to bug 1251431
[20:58] <ali1234> ok. i don't understand how it is related...
[20:58] <brainwash> so we really need to cleanup the code
[20:59] <ali1234> unless you mean it's related in a general sense of "this code sucks and has lots of problems"
[20:59] <ali1234> which is fair enough
[20:59] <brainwash> take a look at the create_root_surface function
[21:00] <brainwash> this function contains the line to blank the screen (after locking it)
[21:00] <brainwash> so it behaves like xscreensaver
[21:00] <ali1234> yeah
[21:00] <brainwash> if you call set_background, you also call create_root_surface
[21:01] <ali1234> ok...
[21:02] <brainwash> and this is bad, because my screen does not remain blanked
[21:02] <ali1234> ok, see that's where you lost me
[21:02] <brainwash> if I call set_background only once, it works
[21:02] <brainwash> screen stays blanked
[21:02] <ali1234> ok, so on startup you mean
[21:02] <brainwash> right
[21:03] <ali1234> startup after yu pressed "lock screen" that is
[21:03] <brainwash> yes
[21:03] <brainwash> the normal screen lock does no allow user switching anyway
[21:03] <ali1234> yeah but that's irrelevant
[21:04] <ali1234> the problem is it sets the background to default, then creates a bunch of widgets, then sets background to the user one
[21:04] <brainwash> so... we can fix many problems with a code cleanup :D
[21:04] <ali1234> but it can't get the user background until after it did all that widget stuff
[21:05] <brainwash> can't we set the background to default only as fallback option, if the user background is not available?
[21:05] <ali1234> yes
[21:05] <ali1234> but that means defering it
[21:05] <ali1234> until after the point where we usually load the user background
[21:05] <brainwash> yes, won't hurt or?
[21:06] <ali1234> well, it might do, because there's no root pixmap until after set_background
[21:06] <brainwash> currently I've simply commented the default background call out
[21:06] <ali1234> yes
[21:06] <ali1234> actually what you need to do is move the set_background to...
[21:07] <brainwash> yeah
[21:07] <ali1234>     if (lightdm_greeter_get_hide_users_hint (greeter))
[21:07] <ali1234> which is much further down the functions
[21:07] <ali1234> around 1890
[21:08] <brainwash> the solution is quite easy
[21:09] <ali1234> go on...
[21:09] <brainwash> looks like you are very interested in fixing this :D
[21:09] <ali1234> it's fairly simple to fix, just a lot of refactoring
[21:10] <brainwash> you are more skilled, I would mess up and break the code :/
[21:10] <ali1234> that's the problem with refactoring things
[21:11] <ali1234> that's why nobody ever wants to do it
[21:11] <brainwash> usually you have some tests to verify the functionality
[21:13] <brainwash> but I'll try to write a patch later (to at least provide a fix for my bug report)
[21:13] <ali1234> part of the problem is that it doesn't just use one pixmap
[21:13] <ali1234> it makes one per screen
[21:13] <ali1234> so then you have to have an array to keep track of them
[21:14] <ali1234> and you have to handle screens getting added and removed
[21:14] <brainwash> ouch
[21:14] <ali1234> currently it does none of this, it just blasts all over whatvever exists "right now" and then leaks it
[21:15] <brainwash> what about the unity-greeter? is it more mature?
[21:15] <ali1234> dunno. it's vala, and huge
[21:15] <brainwash> it's written in vala
[21:15] <brainwash> yes
[21:15] <ali1234> i'd rather fix this code i think
[21:15] <ali1234> i bet unity-greeter has just as many problems
[21:19] <ali1234> actually it's even worse than i thought, because it disconnects from the xserver after dumping the pixmap on it
[21:19] <ali1234> so if you keep a reference to it, it can go invalid without warning
[21:20] <ali1234> this is really hairy...
[21:20] <knome> elfy, ping
[21:21] <brainwash> you should ge a cup of coffee
[21:21] <brainwash> get
[21:21]  * genii readies the coffeepot
[21:21] <ali1234> i just realised this while i was brewing some tea
[21:21] <elfy> s'up knome
[21:21] <knome> elfy, you worked with the community wiki i assume?
[21:21] <knome> elfy, the community *help* wiki
[21:21] <elfy> once or twice
[21:22] <knome> elfy, aha, okay
[21:22] <knome> elfy, i still might need your opinion..
[21:22] <elfy> well - that was a figure of speech :) quite a bit :)
[21:22] <knome> but i'll get back to you later on that
[21:22] <knome> lol
[21:22] <knome> haha, in that case
[21:22] <knome> i'll get to you now :)
[21:22] <elfy> lol
[21:22] <knome> noticed i took a work item on refreshing the frontpage?
[21:23] <knome> https://help.ubuntu.com/community/FrontPageRefresh
[21:23] <knome> that's a brief start
[21:23] <knome> i'm starting with trying to see what kind of stuff would be best grouped together
[21:23] <elfy> ok
[21:24] <knome> how up-to-date is the NewDocs page?
[21:25] <elfy> pretty much worked on constantly
[21:25] <knome> and why that name and not MostPopular or sth
[21:25] <elfy> god only knows
[21:25] <knome> lol
[21:25] <knome> also,
[21:25] <knome> do you think the alphabet-pages could have some kind of shared banner
[21:25] <elfy> last post in the thread a bunch of people working on newdocs was 4 days ago
[21:25] <knome> to link back to the frontpage (NewDocs) and the rest of the alphabets
[21:26] <knome> gtg, brb
[21:26] <elfy> talk to slickymaster about that newdocs thingy - he'll have an idea
[21:41] <knome> okay
[21:42] <elfy> he's done a lot of work with those doing that page
[21:42] <elfy> but what was it you wanted from me?
[21:45] <knome> well, comments about my page
[21:45] <knome> and if you had other ideas and insight what would be useful on the front page, and if there is something you think could be dropped
[21:45] <elfy> ok
 do you think the alphabet-pages could have some kind of shared banner
[21:46] <knome> i'm definitely not forcing any layout or changes that people who are familiar with the wiki do not think are useful, and open to all suggestions
[21:46] <elfy> what did that refer to? the newdocs thing?
[21:46] <knome> yep
[21:47] <knome> all the pages could have a banner that said "Popular posts" and then list all the alphabets
[21:47] <elfy> I'd imagine the only reason it hasn't is that no-one has either not bothered yet - or can't
[21:48] <knome> lol
[21:51] <elfy> I've bookmarked your new page - I'll look tomorrow afternoon when I get back
[21:52] <elfy> but - the current page definitely needs a revamp :)
[21:54] <ochosi> ali1234: there is another greeter based on lightdm-gtk-greeter
[21:54] <ali1234> elfy: on the subject of the wiki and specifically that triage page - i think the descriptions of what bug statuses mean should be removed from that page and merged into Bugs/Status (which is linked near the bottom)
[21:54] <ochosi> it might have some of those issues fixed
[21:55] <knome> eewh, surge protection
[21:55] <ali1234> ochosi: oh? where is it?
[21:55] <ochosi> ali1234: here https://www.google.at/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CDIQFjAA&url=https%3A%2F%2Fgithub.com%2Fkalgasnik%2Flightdm-another-gtk-greeter&ei=TN6LUo0WjNfsBoibgegI&usg=AFQjCNHD3XUgYZOkNz9mE_foxPUMSomhlg&sig2=L2mGPe5-4j1kK_ohW2SGaQ&bvm=bv.56643336,d.ZGU
[21:55] <ochosi> gah
[21:55] <ochosi> sory
[21:55] <knome> ochosi, well done
[21:55] <ochosi> yeah :(
[21:55] <ochosi> ali1234: https://github.com/kalgasnik/lightdm-another-gtk-greeter
[21:56] <ochosi> ali1234: i've also gotten in touch with the author, because the changes seemed quite vast and i'm not sure we'd want all of that
[21:56] <ali1234> hmm yes looks like it has some changes with how screen backgrounds work
[21:56] <ochosi> he replied he might help but he was busy and haven't heard back since
[21:56] <ali1234> well, i can try to port his fixes
[21:57] <ali1234> did you read all my ranting?
[21:58] <ali1234> do you happen to know what revision he forked from?
[21:59] <ali1234> https://github.com/kalgasnik/lightdm-another-gtk-greeter/commit/a21a7e15e77d54fc36042f3589a34193c7d65841#diff-803c5170888b8642f2a97e5e9423d399L129
[21:59] <ali1234> typing in wrong window is bad...
[22:01] <ali1234> wait, is this even a fork?
[22:02] <ochosi> yeah, i read all your rants
[22:02] <ali1234> this code has no resemblance to lightdm-gtk-greeter at all
[22:02] <ochosi> but as i said, i'm not the author and didn't feel comfortable with fiddling with the bits and pieces too much
[22:03] <ochosi> (or at least with the larger bits and pieces)
[22:03] <ali1234> yeah i can't blame you for not wanting to change anything in this code
[22:03] <ali1234> *i* don't want to either
[22:03] <ochosi> it mostly worked so far
[22:03] <knome> elfy, the wiki is impossible to edit!
[22:03] <ali1234> the way it works is a nasty brutal hack
[22:03] <ali1234> it works... no more, no less
[22:03] <ochosi> so we started ironing out some stuff
[22:03] <ochosi> and improved the looks
[22:03] <ochosi> that's pretty much where it is now
[22:03] <elfy> knome: why do you think I said once or twice
[22:04] <knome> ;)
[22:04] <elfy> I hate the wiki :)
[22:04] <ochosi> +1
[22:04] <knome> ochosi, i'm talking about a different wiki!
[22:04] <ochosi> i've started to consider making small previews of the background-submissions just to make the page-loading more bearable
[22:04] <elfy> and don't whatever you do logout of it - it takes a week of sundays to log back in ...
[22:04] <knome> ochosi, i considered the same thing actually
[22:05] <knome> ochosi, and maybe we simply should do Incoming and Accepted
[22:05] <ochosi> wouldn't take very long to do it
[22:05] <ochosi> yeah, as i suggested once...
[22:05] <knome> no, not really
[22:05] <ochosi> ok, how then?
[22:05] <knome> and i said go ahead if you think that's what we need
[22:05] <knome> and then you were "meh"
[22:05] <ochosi> yeah, but i wanted to wait for pleia2 actually
[22:05] <knome> "wouldn't take very long to do it" -- "no, not really"
[22:06] <elfy> knome: can you at some point soon - check the LTS pending blog, fiddle with it if necessary and get it published :)
[22:06] <elfy> not too worried about the other one
[22:06] <ochosi> knome: the good part of that distinction would be that the not-yet-accepted ones would be more visible
[22:06] <knome> ochosi, yes
[22:06] <elfy> right - I'm off now - back tomorrow
[22:07] <ochosi> ali1234: fwiw, i never got around to really testing that other greeter, feature-full as it might be
[22:07] <knome> ochosi, and we could have a naming scheme for the files that makes it easier to handle them
[22:07] <ochosi> ok, i'll start setting up an accepted-page
[22:10] <ochosi> knome: ok, so are there any submissions you wouldn't accept so far for some reason? (apart from the ones with license-issues)
[22:10] <knome> i don't think there is any reason to decline any other at this point
[22:10] <ochosi> yeah, i agree
[22:10] <ochosi> so, naming-scheme
[22:11] <ochosi> easiest is title. but title_author would also work
[22:12] <knome> could even be author_title
[22:12] <ochosi> yeah
[22:12] <ochosi> true, there are many that submitted more than one
[22:12] <knome> titles are just arbitrary... titles
[22:17] <knome> ochosi, i would also make a note to the accepted page that those wallpapers are accepted *submissions*, and that there is no promises of them getting into the release, and that people shouldn't edit that page directly
[22:18] <ochosi> yeah
[22:20] <ochosi> knome: feel like doing a few thumbnails? ;)
[22:21] <knome> send me all the files and i'll batch-convert them.
[22:21] <ochosi> that'll take ages with my connection
[22:22] <ali1234> ochosi: did you add all the "is_locked" stuff?
[22:22] <ochosi> ali1234: yeah, in the last commit (or the one before that)
[22:22] <knome> ochosi, heh.
[22:22] <ali1234> is it's only purpose to trigger the XForceScreenSaver in create_root?
[22:23] <knome> ochosi, what do you want me to do then?
[22:23] <ochosi> ali1234: yeah. the main issue was that i didn't want to write another function to cycle through all displays...
[22:23] <ochosi> knome: download the pics yourself, man! :)
[22:24] <ali1234> ochosi: well my concern is it can only ever be called on gdk_display_get_default() anyway
[22:24] <ali1234> which should always be the same thing
[22:24] <ali1234> so why not just call it once, from main()?
[22:24] <ochosi> sounds quite plausible :)
[22:24] <ali1234> then every instance of is_locked can be removed
[22:25] <knome> ochosi, all of them?
[22:25] <ochosi> knome: all of the accepted ones
[22:25] <knome> uh
[22:25] <knome> what have you done so far?
[22:25] <ochosi> knome: i'm still in process of moving/renaming them
[22:25] <knome> okay
[22:25] <knome> so do you want me to do that once you've moved?
[22:26] <ochosi> as you wish, i mean basically you already know which ones i'm gonna move
[22:26] <knome> well if the moving is fine for you, it's easiest for me to just grab * from one page
[22:27] <ochosi> that's also ok
[22:27] <knome> ok, good
[22:27] <knome> let me know when you're done
[22:27] <ochosi> basically the renaming is the more annoying part
[22:27] <ochosi> sure
[22:31] <ali1234> ok does someone want to try lp:~a-j-buxton/lightdm-gtk-greeter/experimental
[22:31] <ali1234> i think this will fix the locking thing, but not the double drawing background
[22:31] <ali1234> i might be totally wrong though
[22:31] <ochosi> sure, i'll do that as soon as i've finished the monkey job in the wiki...
[22:32] <ali1234> hmm... want a script for that?
[22:33] <ochosi> hm, if you can include creating thumbnails, sure! :)
[22:33] <ali1234> not a problem. what exactly do you need to do? download all submitted images and thumbnail them?
[22:34] <ochosi> that's the one part, the more annoying part is moving some of the submissions to the accepted-page
[22:34] <ochosi> and rename them to author_title
[22:34] <ochosi> so that's hard to script
[22:35] <knome> probably best to suffer of it once
[22:36] <knome> after that it's one or two per time
[22:37] <ochosi> yeah, i mean the script for downloading images and creating thumbs might still be handy
[22:38] <knome> well blah :)
[22:38] <ochosi> i also hate the plaintext links
[22:38] <ochosi> might fix that later
[22:49] <ali1234> did you just delete a bunch of stuff from the page?
[22:49] <pleia2> ochosi is destroying my inbox
[22:51] <ochosi> pleia2: sorry ;)
[22:51] <ochosi> maybe it's time to set up some filter-rules?
[22:51] <ali1234> why is there an application_octet-stream attached to the page?
[22:51] <ochosi> ali1234: yeah, not sure, it's just now getting easier to see all the attachments
[22:51] <ochosi> knome: i think i'm done
[22:52] <knome> ochosi, i'll get to that soon. i need to fix something else first ;)
[22:52] <pleia2> ochosi: normally I want to see :) I just keep getting notifications, whee
[22:52] <ochosi> pleia2: sorry, but the cleanup was direly needed...
[22:53] <pleia2> I know, I kid anyway
[22:55] <ochosi> ali1234: hehe, that octet stream looks like a debian wallpaper
[22:55] <ochosi> http://www.zimagez.com/zimage/screenshot-11192013-115531pm.php
[22:56] <knome> pleia2, i'm the next one to spam your inbox
[22:56] <ali1234> i like it
[22:58] <ochosi> yeah
[22:58] <ochosi> nice'n'spacey
[22:58] <ochosi> pity that there's no author etc
[23:00] <knome> pleia2, ready for another round of spam?
[23:00] <knome> pleia2, ready or not, here it comes
[23:01] <pleia2> si
[23:04] <ochosi> ali1234: ok, locking and blanking still works
[23:04] <ochosi> so far so good
[23:07] <ochosi> ali1234: the fun thing is i wanted to implement it like that in the beginning, but then i somehow thought i have to force the screensaver for each display separately
[23:08] <ali1234> display/screen confusion
[23:08] <ali1234> easily done
[23:08] <ochosi> yeah
[23:08] <ochosi> :/
[23:08] <ochosi> well, thanks!
[23:08] <ochosi> if you could submit it as a merge-request, i can merge it in
[23:09] <ali1234> though i'm not sure why you get away with calling it multiple times for each screen, but calling the whole loop more than once breaks
[23:09] <ali1234> unless of course you never tested on multiscreen :)
[23:09] <ali1234> yeah i can mr it
[23:09] <ochosi> i have a dualhead setup here
[23:10] <ochosi> so that might fix blanking for brainwash hopefully
[23:10] <ali1234> http://paste.ubuntu.com/6445334/
[23:10] <ochosi> knome: ^
[23:11] <knome> they are already uploaded
[23:11] <ali1234> this only downloads and thumbnails them anyway :)
[23:11] <knome> i'm just laying out the page
[23:12] <ochosi> i think i'll keep the download-part of that script around, we could attach a tarball with all backgrounds for convenience
[23:13] <bluesabre> ah
[23:13] <bluesabre> good ol BeautifulSoup
[23:13] <ochosi> hey there bluesabre
[23:13] <ali1234> it will probably crash if there's anything "not an image" attached to the page
[23:13] <bluesabre> when it works, it works well
[23:14] <ali1234> or if someone uploads an image named "do=view&.jpg"
[23:14] <ali1234> actually probably not since it would be escaped
[23:14] <bluesabre> that would be only slightly evil
[23:14] <ochosi> in what package would i find that beautiful soup?
[23:15] <ali1234> python-beautifulsoup
[23:15] <ochosi> gah, i was looking in libpython
[23:15] <ochosi> i'll start testing the wallpapers then
[23:16] <ochosi> just have to add a rm *_250.jpg
[23:17] <ochosi> ali1234: you wouldn't know anything about using the X11 dpms extension?
[23:17] <knome> ochosi, https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Trusty/CommunityWallpapers/Accepted
[23:18] <ochosi> knome: fail: juergendonauer_walkingfishermaninthesunset.jpg_250
[23:18] <knome> fixed already you stupid
[23:18] <knome> :P
[23:18] <bluesabre> lol
[23:18] <ochosi> oh sure, pin it on me! :D
[23:19]  * knome pins
[23:19] <ochosi> damn
[23:22] <ali1234> ochosi: i didn't know anything about any of these things before i started digging :)
[23:23] <ochosi> ali1234: hehe, well same here ;) anyway, thing is that that would be the preferred blanking of the screen, the standby of the display
[23:24] <ali1234> so you want the screen to turn off when it does XForceScreenSaver?
[23:24] <ochosi> yeah
[23:24] <ochosi> cause the VT-switch cause the screen to switch off for a second
[23:24] <ochosi> so ideally it would stay that way
[23:24] <ochosi> instead of "waking up" only to stay blank
[23:26] <ali1234> DPMSForceLevel?
[23:26] <ali1234> http://ftp.x.org/pub/X11R6.9.0/doc/html/DPMSForceLevel.3.html
[23:27] <ochosi> knome: set xfdesktop to change the wallpaper to one of the submissions ;)
[23:27] <ochosi> ali1234: yeah, i'd try DPMSForceLevel(display, DPMSModeOff);
[23:27] <knome> ochosi, huh:P
[23:27] <ochosi> but from what i heard, there are multiple dpms extensions for X11
[23:27] <ali1234> i have no idea how to test this stuff - screensaver/locking is horribly broken here, i had to remove all of it
[23:27] <ochosi> so i started to be a bit doubtful of what would work, it also adds an extra dependency
[23:28] <ochosi> what are you using now?
[23:28] <ali1234> the monitor power switch
[23:28] <ochosi> the proposed solution for xubuntu is light-locker
[23:28] <ochosi> haha
[23:28] <ochosi> that one also wouldnt need the dpms patch i guess
[23:29] <ali1234> for some reason the display still goes blank after a time, but does not turn off
[23:29] <ochosi> well those are different things afaik
[23:29] <ochosi> blanking and standby
[23:29] <ochosi> with potentially different timeouts
[23:29] <ochosi> check "xset q" for your local settings
[23:29] <ali1234> they're all disabled in the control panels
[23:30] <ali1234>   Standby: 0    Suspend: 0    Off: 0
[23:30] <ochosi> not sure what those control panels you're referring to control
[23:30] <ochosi> and in the screensaver part?
[23:30] <ali1234> me either
[23:30] <ali1234> there is no screensaver part
[23:30] <ochosi> rly?
[23:30] <ochosi> funny
[23:30] <ali1234> oh wait
[23:30] <ali1234> timeout: 600
[23:30] <ochosi> that's it
[23:30] <ochosi> 10min
[23:31] <ochosi> a bit short for my taste, but ok
[23:31] <ochosi> so if you enable standby, it'll shut off the backlight of the monitor
[23:31] <knome> bbl
[23:31] <ochosi> (or was it suspend that did that, i'm always confused by those two namings...)
[23:34] <ochosi> bluesabre: btw, i noticed that the parole-docs don't cover the "hidden" playback-shortcuts yet (arrow-keys etc), slickymaster agreed to add them
[23:34] <bluesabre> oh yeah
[23:34] <bluesabre> :D
[23:35] <ochosi> cause those are actually quite important in the docs, as they're not easily discoverable
[23:35] <bluesabre> right
[23:53] <ochosi> ali1234: because you mentioned cross-fading would be only 5 lines, what method would you use exactly?
[23:53] <ali1234> set a timer, draw the background multiple times
[23:53] <ali1234> that was before i really looked at the code though
[23:53] <ali1234> doing this would be a terrible idea since each time you draw the background it leaks a pixmap
[23:56] <ochosi> that just means we have to make our default wallpapers lean ;)
[23:56] <ali1234> no
[23:56] <ali1234> the pixmap is monitor sized
[23:56] <ali1234> contents don't matter, it's not compressed
[23:56] <ali1234> this is what create_root does
[23:57] <ochosi> true (i was kinda kidding there)
[23:57] <ali1234> specifically the pixmap it creates doesn't get freed - by design
[23:57] <ali1234> i'm reading all about RetainPermanent at the moment
[23:57] <ochosi> yeah, that might've been robert_ancell's idea then
[23:57] <ali1234> i can see why it's done
[23:58] <ali1234> if you only set the background once it makes perfect sense
[23:58] <ochosi> yeah, which originally was the case
[23:58] <ali1234> because it stays around after the greeter exits
[23:58] <ochosi> the background-switching was introduced by us (mr_pouit)
[23:58] <ali1234> but if you change the background, you're making a new one each time, and they all stay
[23:58] <ochosi> maybe best to check what unity-greeter does
[23:59] <ochosi> as it also shows user-wallpapers
[23:59] <ali1234> change the background 100 times and you leak 1GB
[23:59] <ali1234> maybe it would be better to only do this RetainPermanent thing once when the greeter exits


[12:25] <sladen> sent
[12:25] <sladen> JohnLea___: I need to go somewhere for the rest of this afternoon
[12:25] <sladen> JohnLea___: I've sent the dreaded email
[12:25] <sladen> JohnLea___: we'll have to wait and see the response
[12:26] <JohnLea___> sladen; thanks for the email and thanks for letting me know, much appreciated
[12:26] <JohnLea___> sladen; I'll cancel this week's meeting
[12:27] <sladen> JohnLea___: yeah, ta


[00:11] <pedro> hi
[00:13] <pedro> hi
[00:13] <pedro> who are you jelmer
[00:22] <pedro> who is awaka here
[00:22] <pedro> give me a poem
[13:49] <xapantu> Hi :)
[18:17] <sjamaan> I am trying to view files on http://bazaar.qastaging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/files but it keeps redirecting endlessly
[18:17] <sjamaan> The "Updating branch..." message doesn't go away either
[18:18] <sjamaan> Is this a known bug?
[18:19] <tsimpson> it kind-of works if you use https://
[18:19] <sjamaan> heh
[18:19]  * sjamaan tries
[18:21] <tsimpson> infinite redirects are obviously not expected though
[18:22] <sjamaan> not expected, but possibly known
[18:22] <tsimpson> staging is working fine though
[18:23] <sjamaan> yeah, I just saw it
[18:23] <sjamaan> I'll use that for my test
[18:23] <sjamaan> Is there a way to fetch a file at "the latest revision" from loggerhead?
[18:23] <sjamaan> I'm trying to construct a raw file URL that downloads this file: http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/view/head:/spiffy.release-info
[18:24] <sjamaan> The "download file" link encodes all sorts of codes
[18:25] <sjamaan> replacing "view" with "download" just causes an error
[18:25] <tsimpson> I think you're supposed to use bzr for that ;)
[18:26] <sjamaan> Is there a http-only way to do it though?
[18:27] <tsimpson> well bzr can use http
[18:27] <sjamaan> Does launchpad offer that?
[18:27] <tsimpson> bzr cat http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/spiffy.meta
[18:28] <tsimpson> the lp: address shortcut uses bzr+ssh, but there's nothing stopping you from using the "real" URL
[18:28] <sjamaan> hm, that does some magic apparently because a straight GET doesn't fetch the file
[18:28] <tsimpson> yes, it uses bzr :)
[18:28] <sjamaan> But why does it say http then?
[18:28] <tsimpson> bzr the program, not "the protocol"
[18:28] <sjamaan> yes
[18:29] <sjamaan> But the URI has a prococol of http
[18:29] <tsimpson> bzr can sit on top of http just fine
[18:29] <sjamaan> But that resource isn't really there as a normal HTTP resource
[18:29] <sjamaan> curl http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/spiffy.meta  gives a 404
[18:29] <tsimpson> bzr figures out how to get the file and just downloads it's "real" URL
[18:30] <tsimpson> it's all done over HTTP, bzr it just knows how to get the real file from the repo
[18:31] <sjamaan> What exactly is done over HTTP?
[18:31] <sjamaan> And why doesn't that URL work with a HTTP GET request?
[18:31] <tsimpson> everything is done over HTTP
[18:31] <tsimpson> bzr breaks the URL apart at the branch and figures out how to get the file from the rest of the URL
[18:32] <sjamaan> Is there a way to figure out that URL without digging in the bzr sources?
[18:32] <tsimpson> not easily, that's why bzr is there
[18:32] <sjamaan> Or is it not an URL but a special header or something?
[18:33] <tsimpson> you can use the python API if you don't want to actually run bzr directly
[18:33] <tsimpson> bzr does nothing to the HTTP protocol, it just uses it as a transport mechanism
[18:34] <sjamaan> hm, ok
[18:34] <tsimpson> file:// http:// bzr+ssh://, it doesn't matter as long as it can send a request and get some data back
[18:34] <sjamaan> But there's no way to get an URI like  http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/download/head:/spiffy.releaseinfo-20110326171946-vqfrwsi51nna9bj3-46/spiffy.release-info without going to http://bazaar.staging.launchpad.net/~peter-bex/+junk/spiffy-bzr-test/view/head:/spiffy.release-info ?
[18:37] <tsimpson> no, it's a generated URI
[20:25] <Meths> Why is code browsing looking sucky again?
[20:27] <lifeless> do you mean bazaar.launchpad.net ?
[20:29] <Meths> Yep
[20:29] <lifeless> what do you mean by being sucky?
[20:29] <Meths> The same line spacing I filed a bug and you fixed before.
[20:32] <lifeless> ah
[20:32] <lifeless> new theme I guess
[20:32] <lifeless> want to file a new bug? I'll nudge our UI dude on monday
[20:33] <lifeless> (it may be missing css, or it may be a defect in the new theme)
[20:33] <Meths> File a new bug or reopen the old one?
[20:33] <lifeless> new bug
[20:33] <lifeless> always a new bug :)
[20:33] <Meths> k
[20:34] <Meths> Will always a new bug translate into a process that gets this tested in future rather than always just another new bug?
[20:36] <lifeless> it will depend on the cause
[20:36] <lifeless> we deploy loggerhead on two machines
[20:36] <lifeless> one machine just serves the css
[20:37] <lifeless> the other just serves the dynamic bits
[20:37] <lifeless> I suspect the former machine hasn't been deployed to
[20:37] <lifeless> because the other stuff on the former machine is not able to updated without downtime
[20:37] <lifeless> if that the case, updating our process/docs should solve this
[20:37] <lifeless> if its something else - well, will analyse
[20:41] <Meths> Well CSS was the bug before so if it's CSS the docs didn't get updated last time.  New bug filed.
[20:46] <lifeless> thanks
[21:40] <akoskm> evening
[21:43] <akoskm> I built some packages through launchpad for ubuntu - maverick, is it possible to build packages from the same source to older releases of ubuntu?
[22:58] <aroman> hello, are there bindings to access launchpad in any languages other than python?