[00:00] <flocculant> knome: and just how long do you think we should play this game with them?
[00:00] <flocculant> I've got to have a cut off point
[00:00] <knome> if they won't allow the core name, let's just change it then
[00:00] <knome> but if they don't, they'd better have a good argument
[00:00] <flocculant> and given they are just playing games then my cut off off point is the 1st
[00:00] <flocculant> of January
[00:01] <knome> it's their infrastructure; i'm sure they'll happily let us run our own and call our products whatever we like
[00:01] <knome> do you have a link to LP where the naming discussion is?
[00:01] <flocculant> the more I see of this issue the more I can see why people were /o\ over other debian issues
[00:02] <flocculant> and yes it is the same ;)
[00:02] <flocculant> knome: no - the name discussion was with adam in -release
[00:02] <knome> maybe.
[00:02] <knome> ok, do you remember the date?
[00:02] <flocculant> 2015/4
[00:03] <Unit193> infinity didn't seem to care, just wanted to point it out.
[00:03] <flocculant> I've given up tbh on caring much, my position is if they eventually come through a day or so prior to release then that's really too bad and much much too late
[00:04] <flocculant> yea
[00:04] <Unit193> I'll poke again, I suppose.
[00:04] <knome> i haven't seen anybody explicitly say "no"
[00:04] <flocculant> then slangasek disapproved - and has ignored it since
[00:04] <flocculant> well
[00:05] <Unit193> And wonder why they don't get contributors?
[00:05] <flocculant> other than an apparent 'it's on my queue' comment to Unit193
[00:05] <flocculant> which is as meaningless as any other comment
[00:07] <flocculant> oh good lord is the wiki down again
[00:07] <flocculant> should make sure we bring this up on the pointless CC chat I guess
[00:08] <knome> the wiki works for me.
[00:08] <flocculant> mmm
[00:08] <flocculant> https://wiki.ubuntu.com/CommunityCouncilAgenda
[00:09] <flocculant> that one?
[00:09] <knome> that too
[00:09] <flocculant> must be local for some reason then - I can get anywhere else
[00:12] <flocculant> or firefox - chromium landed fine
[00:12] <knome> i would personally find out if this is about the name or not
[00:12] <knome> if it's about the name, then get on with it and change to something else
[00:12] <knome> if it's something else... well, then just push forward
[00:14] <flocculant> cc meeting is 2 working days before b1 freeze so that's pointless
[00:14] <knome> and figure out possible blockers and see what we can do with it
[00:14] <knome> i don't think the CC is the right council to resolve this anyway
[00:15] <flocculant> I'll pinh mhall119 for the last 30 minutes of this discussion
[00:15] <flocculant> ping
[00:15] <knome> or if somebody feels like we'd like to get them involved, we can just poke them outside a meeting
[00:15] <knome> yes, something like that ^
[00:15] <flocculant> maybe not - but given they are all on holiday till god only knows when - who do we poke?
[00:16] <knome> i don't know
[00:16] <flocculant> sorry, but I think this is about the name - perhaps amongst themselves - but ...
[00:16] <knome> then they should clearly state that to us
[00:16] <flocculant> and any reason to slow is enough
[00:16] <knome> in which case we will come up with a new one
[00:16] <flocculant> I have no trust in them anymore tbh
[00:17] <flocculant> as a 'group'
[00:17] <knome> i guess i can see that, but otoh, that attitude doesn't help at all (as you also know)
[00:17] <knome> we can blame them to the end of the world, but that won't make them do decisions we want
[00:17] <knome> might do quite the opposite
[00:18] <flocculant> knome: currently we're waiting for one person to find time in their queue
[00:18] <knome> if that's the real status (and they just don't want to do it because of the name), then we should wait
[00:18] <knome> we should also be in touch with them and probably get an ETA at some point
[00:18] <flocculant> right now - they work for me, it's taking too long so I don't even have to think about testing it ;)
[00:18] <knome> but i don't think there is much more to do
[00:19] <flocculant> as far as I now 'we' can't do more than we have
[00:19] <flocculant> Unit193: is that right ^^ ?
[00:19] <knome> not much at least
[00:19] <flocculant> we did what they asked
[00:20] <knome> yes, i have the same point of view to it
[00:21] <flocculant> anyway - bed for me now :)
[00:22] <knome> yep, have a good night and don't worry too much about things
[00:23] <flocculant> oh I won't :)
[00:23] <flocculant> if it turns up in March - too late ;)
[00:23] <knome> let's target for january.
[00:24] <flocculant> mmm
[00:24] <flocculant> night :)
[00:24] <knome> good night!
[00:31] <Unit193> Well we could fix it so it applies cleanly, but I've already done that before and don't see a reason to do so again unless it'll be reviewed before I'd have to fix it yet again.
[00:43] <knome> at least i'd make sure the name isn't a showstopper before doing that.
[00:44] <Unit193> I'd have thought they'd say that...
[01:16] <Unit193> flocculant: Hi.  So I'm still activly using Xenial somewhere, but haven't done much reporting except for the upgrade.  Is there something specific there that'd help you, or should I just continue to mention things/file reports as they crop up?
[07:29] <flocculant> Unit193: just carry on as you are is great :)
[13:39] <knome> some improvements about to land to xubuntu.org
[13:39] <knome> as soon as the IS team pushes the new branch revision
[13:51] <knome> bbl
[19:37] <pleia2> ooh, rt tickets being addressed \o/
[19:57] <knome> yup
[21:45] <mhall119> flocculant: I read the backlog, but I don't understand the problem or it's context, can you give me a tl;dr?
[23:31] <knome> mhall119, we've been waiting for a merge since september; merging this change would enable a new version of xubuntu (named "xubuntu core") to be built and thus appear on cdimage.ubuntu.com; we're not exactly sure what is taking so long
[23:31] <knome> mhall119, one possibility is the naming; some concerns have been raised because it conflicts with "ubuntu core", but afaik, nobody has said that's the reason
[23:32] <knome> mhall119, another possibility is that people are simply busy
[23:32] <knome> mhall119, this is more problematic for us every day because as long as the official builds aren't up, we can't do official testing


[01:13] <karni> arune: fixed
[01:14] <karni> arune: I tested, but feel free to test again.
[02:24] <karni> Night!
[09:09] <arune> karni: works! thanks!
[09:10] <arune> karni: do you know where the problem was?
[09:18] <JamesTait> Good morning all! :-D
[09:20] <mandel> morning!
[09:44] <nrosvall> Hi
[09:45] <nrosvall> Is there c++ API for ubuntuone? I can only find one for Python from developer.ubuntu.com
[10:42] <mandel> nrosvall, witch os?
[10:42] <mandel> nrosvall, and what exactly do you want to do?
[10:42] <nrosvall> Ubuntu and well something like this http://developer.ubuntu.com/resources/app-developer-cookbook/ubuntu-one/adding-ubuntu-one-files-support-to-your-app/
[10:45] <mandel> nrosvall, hm... I see, all that is exposed over dbus but we never wrote a 'client api' in anyother lang (the python example is importing from the u1 project directly)
[10:46] <mandel> nrosvall, I think I can help you with that, what c++ framework are you using?
[10:46] <nrosvall> QT
[10:47] <mandel> nrosvall, awesome! hehe just what I was hoping for, writing c++ wrappers with Qt for the dbus methods is not hard, but very very tedious...
[10:48] <mandel> nrosvall, I might be able to write some during the weekend... or even earlier
[10:50] <nrosvall> oh that would be awesome
[10:50] <mandel> nrosvall, can you let me know witch methods you are interested in? that way I can start with those and that way I wont block you
[10:50] <nrosvall> no hurry though, Im just starting. im a long time windows developer and pretty much moving to develop software for Ubuntu
[10:51] <nrosvall> but it really would be nice to have some qt dbus examples for ubuntu one
[10:52] <mandel> nrosvall, well, dbus in qt is a little annoying sometimes, ideally we would want a wrapper that performs the call to dbus in an async manner and uses a pending call watcher to emit a signal when done, that way the app will never block for possible slow requests
[10:53] <nrosvall> hmm I guess I could just use some rest client with c++
[10:54] <mandel> nrosvall, the rest client is not as good to me hones, best way is to talk to the daemon directly, I can deal with the dirty ugly details :)
[10:54] <nrosvall> yeah :)
[10:59] <gatox> good morning!
[10:59] <mandel> gatox, buenas! o/
[11:01] <mandel> gatox, I have been thinking, maybe you have had problems with unity compilation due to the new pre-compiled headers feature that was added to speed up the compilation times
[11:01] <mandel> gatox, have you tried disabling it?
[11:01] <gatox> mandel, aja! jeje nop.... how do i do that?
[11:02] <mandel> gatox, there was an internal mail sent to canonical tech telling how to do it.. are you in that list?
[11:02] <gatox> mandel, ahhhh right...... i'll look it up
[11:02] <gatox> found it.......
[11:02]  * gatox reading....
[11:03] <mandel> gatox, do you have the problems with trunk?
[11:03] <gatox> mandel, nop
[11:04] <mandel> gatox, care to pastebin the error?
[11:04] <gatox> the nop was for problems with trunnk
[11:04] <mandel> gatox, so you have no problems with trunk you say?
[11:04] <mandel> gatox, but with my branch?
[11:04] <gatox> mandel, yes
[11:05] <mandel> gatox, lets do this in private to reduce the noise here :)
[11:26] <nantou> chaselivingston,
[11:30] <nantou> anyone?
[11:35] <beuno> nantou, what's up?
[11:35] <nantou> its about my non working ubuntuone account
[11:36] <nantou> chaselivingston, was trying to help me yesterday, but I had to go
[11:36] <beuno> nantou, it's a bit early for chaselivingston, he'll be here in a couple of hours
[11:36] <nantou> are you an admin beuno ?
[11:36] <beuno> nantou, sort of maybe. What problem are you having?
[11:37] <nantou> thunderbird and the regular ubuntu one directories dont share the same data
[11:37] <nantou> I am missing 1.2 GB of data
[11:37] <nantou> email<EMAIL_ADDRESS>[11:38] <beuno> nantou, I assume chaselivingston recovered the deleted folders for you?
[11:38] <nantou> beuno, we didnt talk that much, I have no idea
[11:39] <nantou> im signing in again to see what happens
[11:39] <beuno> rye, ping?
[11:39] <beuno> nantou, you were syncing the thunderbird folder?
[11:39] <beuno> it doesn't look like you were syncing anything
[11:39] <rye> beuno: pong
[11:40] <beuno> rye, can you take over here?
[11:40] <rye> reading
[11:40] <beuno> thanks
[11:40] <nantou> beuno, hoiw much data do I have at the moment? 9MB or 1.2 GB?
[11:40] <beuno> nantou, 0 bytes
[11:40] <rye> nantou: i'll take it from here
[11:40] <nantou> ok...
[11:41] <rye> nantou: sorry, were you discussing the issue with chase here or in a support ticket?
[11:41] <nantou> the former
[11:43] <rye> nantou: ok, so at the moment the admin interface shows that account<EMAIL_ADDRESS>has 0 bytes, it does not have a UDF for thunderbird attachments so it looks like you have another account with us, you mentioned that it uses an old e-mail, what is the new one?
[11:43] <rye> nantou: or if it was a new e-mail address, what is the older one
[11:43] <nantou> andersen75 is the new one
[11:43] <nantou><EMAIL_ADDRESS>is, was the old one
[11:44] <nantou> you may delete it if you wish
[11:44] <nantou> "syncing the cloud to your computer" the ubuntuone interface has been like that for 6 minutes already, ain't that too much?
[11:45] <rye> nantou: ok, that account is where the 1.3Gb of data are (hihihi one). Ok, as I understand you have created a different account for a new e-mail which is most likely not what you wanted
[11:45] <nantou> file sync error, local and server roots are different, ROOT MISMATCH
[11:45] <nantou> rye, please delete account "hihihi100", I will re upload it all to the new one
[11:47] <rye> nantou: here's the entry about root mismatch - https://one.ubuntu.com/help/faq/what-does-the-root_mismatch-error-mean/
[11:48] <rye> nantou: what you will want to do is to back up all the Ubuntu One data you have (take it away from Ubuntu One directory), shut down ubuntuone - u1sdtool --quit and remove ~/.local/share/ubuntuone  directory
[11:48] <nantou> ok...
[11:49] <nantou> rye, --> u1sdtool --quit and remove ~/.local/share/ubuntuone <-- is the actual command, right?
[11:50] <rye> nantou: command - u1sdtool --quit
[11:50] <rye> nantou: after that command completes, you may remove ~/.local/share/ubuntuone directory
[11:51] <rye> nantou: after this you can start ubuntuone again - u1sdtool --start and put files back into Ubuntu One directory
[11:51] <nantou> i have executed "u1sdtool --quit", ubuntuone-syncdaemon stopped.
[11:52] <nantou> now I am going to execute "u1sdtool --remove ~/.local/share/ubuntuone"
[11:53] <rye> nantou: uhm, no, "rm ~/.local/share/ubuntuone" is what you will want but you can also rename the ~/.local/share/ubuntuone directory (e.g. mv ~/.local/share/ubuntuone ~/.local/share/_ubuntuone
[11:53] <rye> )
[11:53] <nantou> rm: cannot remove `/home/dexter/.local/share/ubuntuone': Is a directory
[11:53] <nantou> sudo?
[11:55] <mandel> nantou, no, use rm -Rf and the dir
[11:56] <mandel> nantou, I bet you forgot the -R, right?
[11:56] <nantou> Ill be off for an hour, a student came in
[11:56] <nantou> possibly
[11:56] <nantou> tschüss
[11:56] <rye> nantou: ah, sorry, yes,  -rf for rm, but mv is ok
[13:05] <nantou> lesson is over im back
[13:06] <nantou> I have executed rm -Rf ~/.local/share/ubuntuone
[13:06] <nantou> do I look good to go?
[13:09] <karni> arune: We haven't identified the exact problem yet, all I can say it was an issue on the server. We rolled back, so that users don't suffer from this problem.
[13:10] <nantou> rye, how does my account look now? im syncing
[13:12] <nantou> can any admin tell me how bad/good does my account look?
[13:13] <rye> nantou: 17Mb used now
[13:14] <rye> nantou: and growing
[13:14] <nantou> no trace of the old hihihi100 one?
[13:15] <rye> nantou: we are not yet able to completely delete the accounts. I will need to get an update about what's the priority for account removal implementation
[13:27] <nantou> a...
[13:33] <arune> karni: ok, then probably not only I was affected I assume
[13:34] <karni> arune: Exactly. This is why I appreciated your cooperation so much :)
[13:34] <arune> karni: let me know if you need more help in this issue, testing a new version etc
[13:35] <karni> arune: We've decided on the solution that we know also works elsewhere, so we're good. Thank you :)!


[00:00] <fefd> impish
[00:03] <fefd> it was never installed, because it has 6 new dependencies which also were not installed, and I never did autoremove
[00:04] <fefd> maybe it's a bug in installer, but I cba reinstalling to check
[00:19] <fefd> also, why the heck installer made a swap file on a ssd?
[00:29] <zenof> fefd: well, as it's a swapfile, it's easy to disable it, if you really wish to. on the other hand, as long as you have a reasonable amount of RAM , the write load to the ssd should be nothing to worry about, in terms of lifespan.
[00:30] <TJ-> Kernel prefers some swap to avoid sudden OOM; you can adopt zram swap to spit the difference
[00:37] <pycurious> When I do history on my machines, I would like to keep tract of when each command was issues for each user (all users). How can I do that?
[00:40] <TJ-> pycurious: you mean timestamps?
[00:40] <pycurious> TJ-: yes - commands issued with timestamps.
[00:40] <pycurious> TJ-: for all users.
[00:41] <TJ-> pycurious: see "man bash" and HISTTIMEFORMAT
[00:42] <pycurious> TJ-: I think that is per user basis. I would like to record that for every user on a system I configure. Is there a way to do that? That way I can go and check what commands were issued by whom at what time?
[00:43] <TJ-> pycurious: you can't do that, only in the per-user $HOME/.bash_history but you can set HISTTIMEFORMAT for system-wide operation
[00:44] <pycurious> TJ-: how do i set HISTTIMEFORMAT for all users on a system ?
[00:44] <TJ-> pycurious: as "man bash" shows under FILES: "/etc/bash.bashrc"
[00:47] <fefd> use proprer tools like auditing
[00:51] <pycurious> TJ-: that worked - thanks
[00:51] <pycurious> fefd: are there any audit tools that allow all command logging to be inspected?
[00:54] <TJ-> py auditd ... https://linux-audit.com/configuring-and-auditing-linux-systems-with-audit-daemon/
[01:01] <pycurious> TJ-: not sure how i can use auditd to log every command that users fire. It seems like its more for auditing changes to particular files (passwd for example) - am i mistaken?
[01:02] <TJ-> pycurious: it can do lots of things, including logging all commands
[01:07] <TJ-> pycurious: for commands being executed, a rule like "-a exit,always -F arch=b64 -S execve" to capture the execve syscall
[02:21] <AcrnAnmly> hello, is there someone that can assist in sorting out what I believe is an lvm issue after updates?
[02:22] <AcrnAnmly> I'm not quite sure where to look next.
[02:22] <AcrnAnmly> I think something's wrong with the initramfs environment?  Basically, when booting the system normally, it says that it can't find the volume group, /dev/mapper/<vgname>-root can't be found, and drops to the busybox shell
[02:23] <AcrnAnmly> but if I boot off of live media and examine the drive, I can access everything perfectly fine
[02:23] <AcrnAnmly> it sees the volume group and the mapper device, and I can mount it successfully and seem to be able to access everything
[02:23] <AcrnAnmly> but running lvm pvs or lvm lvs in the initramfs just comes back empty
[02:35] <yukiup> i'm not that knowledge able but could it be grub?
[04:55] <cammera> Hey, does anyone know if ubuntu focal is going to get kernel 5.15 at some point?
[04:55] <cammera> I use ntfs partitions a lot so having better performance would be a huge thing for me
[04:58] <Bashing-om> !Info linux-generic-hwe-20.04 focal
[05:09] <Bashing-om> cammera: Looks like one may get the 5.15 kerenl with 22.04's second point release in focal as an HWE update.
[05:11] <marcoagpinto> 22.04LTS!
[05:12] <marcoagpinto> just in a few months!
[05:12] <marcoagpinto> :)
[05:12] <cammera> Oh
[05:12] <cammera> Has anyone here tested it, is ntfs faster
[05:28] <noj> Hi all just a quick question. Why couldn't i find hexchat in the ubuntu software centre. i had to run "sudo apt install hexchat"? i did search "software" and then enter and enable the "multiverse" as a source and in the past this has been enough to make it show up when searched for in the software centre (GUI)
[05:29] <noj> Ubuntu 20.04.3 LTS
[05:32] <guiverc> noj, no idea (typing into hexchat here actually)  but it's an old GTK2 app where GTK2 is deprecated
[05:33] <noj> ;)
[05:33] <Bashing-om> !info hexchat focal | noj
[05:33] <noj> ty
[05:39] <noj> anyone know of a general computer help channel on freenode, general not just mac win linux other
[05:39] <noj> like one aimed at my grandma
[05:40] <guiverc> noj, very few of us use freenode these days
[05:40] <noj> lol im not on freenode am i
[05:41] <noj> insert this network please
[05:41] <guiverc> that's not a Ubuntu support question, Ubuntu off-topic maybe a better place than this room
[05:42] <guiverc> #ubuntu-offtopic ^
[05:44] <noj> ;) roggi
[07:17] <Guest30> I just did a fresh install of 20.04.3 and when I try to run apt-get update I get a bunch of hash mismatches
[07:17] <sp234> i've been trying to get mpv to work with windows 11 but i keep recieving this error
[07:17] <sp234>  (+) Video --vid=1 (*) (h264 1280x720 25.000fps)
[07:17] <sp234>  (+) Audio --aid=1 (*) (aac 6ch 48000Hz)
[07:17] <sp234> error: XDG_RUNTIME_DIR not set in the environment.
[07:17] <sp234> error: XDG_RUNTIME_DIR not set in the environment.
[07:17] <sp234> error: XDG_RUNTIME_DIR not set in the environment.
[07:17] <sp234> Error opening/initializing the selected video_out (--vo) device.
[07:18] <Guest30> the file size of the download matches but the hash doesn't.
[07:18] <Guest30> I have never encountered this error before.
[07:19] <sp234> i don't understand why mpv is not working, does it have something to do with the gui?
[07:19] <Hash> mpv is a videe player
[07:19] <Hash> Windows is a MS OS
[07:20] <Hash> If you want help for Ubuntu, you have to use ubuntu. We can't support mpv on windows 11
[07:21] <sp234> i am using ubuntu 20.04 LTS
[07:21] <Hash> sp234 | i've been trying to get mpv to work with windows 11 <-
[07:22] <Hash> I am confused
[07:22] <sp234> sorry let me clarify
[07:23] <sp234> I am using ubuntu 20.04LTS on windows11
[07:24] <refwef> sp234 wsl?
[07:24] <sp234> yeah wsl
[07:25] <refwef> sp234 you're following the steps here? https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
[07:26] <sp234> no i did not, I will try them now thank you
[07:26] <refwef> np
[07:33] <sp234> im still recieving an error when i run one of the Linux Gui apps for example:
[07:33] <sp234>  xcalc
[07:33] <sp234> Error: Can't open display:
[07:34] <sp234> wait a sec brb
[07:45] <sp234> looks like i still can't open any Linux gui apps even after following the steps on https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps
[07:46] <sp234> still recieving the error Cannot open display:
[08:00] <ducasse> !wsl
[08:00] <ducasse> sp234: ^^
[08:00] <ducasse> there was a separate channel for wsl, dunno if there still is
[08:01] <sp234> ducasse: I already installed wsl and its on version 2
[08:03] <ducasse> yeah, sorry, there used to be a mention of another channel there, but i guess that's gone
[08:04] <ducasse> sp234: there is #windows-wsl - have you tried there?
[08:07] <sp234> ducasse: i doubt wsl is the problem. I verfied wsl version via powershell
[08:08] <ducasse> i suspect this is a wsl problem, not an ubuntu problem
[08:11] <sp234> ducasse: maybe... ill check up with the wsl group as well
[08:11] <ducasse> i definitely suggest you try it
[08:29] <TattooedTech> sp234: Are you running the right build of Windows 11? Gui support under WSL requires Windows 11 Build 22000 or higher
[08:34] <sp234> TattooedTech: its on windows 11 build 22000.318
[08:36] <sp234> im actually really stumped on this one
[10:30] <SteelRose>  Hi guys! I use an Ubuntu 20.04 as local repo for both Ubuntu 20.04 and CentOS 8. If it were a CentOS box I could run createrepo_c after the RPMs complete dowloading but there is no such thing in Ubuntu... I've seen some attempts to port the tool to Ubuntu but I cannot even compile it from source or install it from a DEB due to some missing libs ...  has anyone here tacked this issue before? Thanks !
[10:32] <ens> i've put an nvme m2 drive into my hp laptop. it is now alongside the previously installed sata ssd. the nvme shows up as 'sdb' when booting... shouldn't it be something like 'nvme0' ? i'm wondering if it is using some kind of slower hardware protocol.
[10:39] <lotuspsychje> ens: check your; sudo fdisk -l perhaps?
[10:42] <XATRIX> Hi, can you advice ? I'm using XFCE as a window manager. And i have faced with a trouble. My google chrome window oversizes after i do minimize on. Only google chrome. No other.
[10:43] <XATRIX> it's normal - https://imgur.com/nPdTMLQ.png
[10:43] <XATRIX> after restore from minimized - https://imgur.com/zhlllna.png
[10:43] <XATRIX> only reload of browser can help to solve this
[10:46] <ens> lotuspsychje: actually upon doing further reading... i realise these might actually be SATA m.2 ssds seeing as they have 3 prongs not 2.
[10:46] <ens> rather than nvme
[10:55] <ledeni> XATRIX, did you try to select with right mouse button gnome chrome and see options
[10:56] <guiverc> XATRIX, Xfce is a desktop, it uses Xfwm4 as it's WM/window manager (by default)
[10:57] <XATRIX> guiverc: sorry. yea
[10:58] <XATRIX> ledeni: i'll try it
[10:58] <XATRIX> nope, doesn't help me much
[11:01] <ledeni> XATRIX, then try to autohide bottom panel if is possible
[11:14] <KBar> XATRIX, bug #1940707 might be related.
[11:15] <KBar> I, too, encounter a similar problem very often.
[11:15] <KBar> I couldn't find a way to fix it, though.
[11:15] <KBar> Very annoying indeed.
[11:56] <XATRIX> KBar: it is Xfwm related ? Or the native Ubuntu's manager ?
[11:56] <XATRIX> And, it not seems to be. My windows become messed ASAP. Not after reboot :)
[11:57] <KBar> XATRIX, most likely xfwm4.
[11:57] <XATRIX> Ok, i'll dig in
[12:14] <varaindemian> security wise what are the differences between ubuntu X.X.y-1 and X.X.y? Do you get security updates for both?
[12:14] <varaindemian> at the same time?
[12:14] <varaindemian> should I upgrade?
[12:15] <varaindemian> Example given: 18.04.1 vs 18.04.2
[12:15] <KBar> Stable releases only receive security/critical updates.
[12:15] <KBar> So yes, you should update.
[12:16] <lotuspsychje> always up to date indeed
[12:16] <KBar> 18.04.1 to 18.04.2 is just an update, not an upgrade.
[12:16] <lotuspsychje> !uptodate
[12:16] <KBar> 18.04 to 20.04 would be an upgrade.
[12:17] <varaindemian> so if a computer has 18.04.2 and another 18.04.5 then 18.04.2 did not issue upgrade?
[12:17] <varaindemian> so it does not have the latest security patches?
[12:17] <KBar> varaindemian, https://wiki.ubuntu.com/PointReleaseProcess
[12:18] <KBar> https://askubuntu.com/questions/106159/what-are-point-releases-in-lts-versions
[12:18] <varaindemian> KBar: where should I look?
[12:19] <varaindemian> I am only interested in the last digit - 18.04.x vs 18.04.x+y
[12:21] <KBar> varaindemian, say you have firefox and thunderbird at version 45.1 when ubuntu 21.11 is released. after three months, there are some updates to some packages, and now firefox and thunderbird are at version 46. 21.11.1 would include all of the updates, so fresh installations don't miss out on them and don't have to download everything. It's already in.
[12:22] <KBar> varaindemian, if you were on 21.11 and to install all of the updates, your system would automatically bump up to 22.11.1
[12:22] <varaindemian> KBar: so only applications are affected
[12:27] <KBar> Everything will remain mostly the same.
[12:27] <KBar> No big changes or added/removed features.
[12:28] <varaindemian> yeah, but security updates are not implemented..
[12:29] <KBar> What do you mean?
[12:30] <varaindemian> KBar: 18.04.2 is outdated compared to 18.04.5 security-wise
[12:30] <KBar> Of course it is. The numbers tell that already.
[12:31] <KBar> varaindemian, if you installed 18.04 right in the beginning and kept updating every day. You wouldn't notice a difference up until today.
[12:31] <varaindemian> KBar: do you have a link where this is exmplained?
[12:32] <KBar> varaindemian but your version would say 18.04.5/6/7
[12:32] <varaindemian> so the user with 18.04.2 did not issue the upgrade command
[12:33] <varaindemian> if you issue only update your system will get the 18.04.5 version?
[12:35] <KBar> varaindemian, I just gave two links. Point releases are updates, not upgrades. Depends on the initial state of your system.
[12:35] <varaindemian> KBar: so you still get security updates by issuing update without upgrade
[12:36] <KBar> varaindemian, 1) you can keep gradually updating and reaching 18.04.whatever 2) you can never update and update all at once today and reach 18.04.whatever 3) you can grab an up-to-date ISO and reinstall with all updates already baked in and your system will be 18.04.whatever
[12:37] <KBar> varaindemian, yes. Though `apt upgrade` is confusing, it will just update your packages and install security updates/bug-fixes.
[12:37] <KBar> That's all.
[12:37] <KBar> There are exceptions, of course.
[12:39] <KBar> But this is generally how updates in Ubuntu work.
[13:02] <andi87> Hej, I accidently removed the network-manager and probably some other stuff when I was trying to remove teamviewer. I was able to reinstall network-manager via live-cd, but my bluetooth adapter (which is the same as the wifi-adapter) isn't recognized anymore. Does anyone have an idea?
[13:19] <KBar> andi87, what were the commands exactly?
[13:20] <KBar> andi87, look at /var/log/apt/history.log
[13:20] <KBar> andi87, you can restore everything back by reinstalling packages that got removed.
[13:21] <andi87>    44  dpkg -l | grep team
[13:21] <andi87>    45  sudo apt-get purge teamviewer
[13:21] <andi87>    46  sudo apt-get remove teamv*
[13:25] <andi87> KBar  ah, allright. The history.log file shows the whole terminal output, didn't knew that. So these are the packages: Commandline: apt-get remove teamv*
[13:25] <andi87> Requested-By: andi (1000)
[13:25] <andi87> Remove: network-manager-pptp:amd64 (1.2.8-2), libteamdctl0:amd64 (1.30-1), network-manager-gnome:amd64 (1.8.24-1ubuntu3), network-manager-config-connectivity-zorin:amd64 (1.0-1), network-manager:amd64 (1.22.10-1ubuntu2.2), network-manager-openvpn:amd64 (1.8.12-1), network-manager-openvpn-gnome:amd64 (1.8.12-1), network-manager-pptp-gnome:amd64
[13:25] <andi87> (1.2.8-2)
[13:27] <KBar> andi87, what version of Ubuntu?
[13:29] <andi87> KBar Using Ubuntu 20.04, Gigabyte GC-WB1733D-I as Wifi & BT card.
[13:31] <KBar> andi87, you're going to reinstall all of those packages. And don't use wildcards like that.
[13:31] <KBar> *going to have to
[13:32] <andi87> KBar yes, that was a bad idea
[13:32] <andi87> KBar thanks
[13:33] <KBar> yw
[13:38] <BinarySavior> having trouble with DNS config on Ubuntu.  https://bpa.st/MOTA
[13:38] <BinarySavior> <IP_ADDRESS> is my default gateway
[13:51] <mrcoffee> Hi. How do I play a .plist file in Ubuntu?
[13:51] <mrcoffee>  It's a music playlist..
[13:55] <BluesKaj> Hi folks
[13:55] <p13> mrcoffee: isn't plist a macos preference list xml file?
[13:55] <mrcoffee> Yes, i think it's that..
[13:56] <p13> if you open it in a text editor, what do you see?
[13:58] <mrcoffee> It's an mp3 list with p f t A D fields with some other data like author etc..
[13:58] <mrcoffee> p is the link D the duration A the author..
[13:59] <mrcoffee> ...
[13:59] <p13> does it link to the source files?  If not ... there won't be much to play
[14:14] <KBar> mrcoffee libplist3, libplist-utils
[14:14] <KBar> may help you convert and possibly read/write
[14:18] <p13> mrcoffee: i guess you missed the answer by KBar (you got disconnected)
[14:19] <p13> check out libplist3 and libplist-utils
[14:28] <ledeni> mrcoffee, just use this play list ---> http://felloff.net/usr/cinap_lenrek/music/9front/playlist.m3u
[14:55] <user42_> quick question about the IRC RFC(2812), Im workin on building my own serv and had that question about replies (took ADMIN Command as example). It says that you have to send multiple replies. Does it concatenate the content of each reply in one and send it back to us. Or really build differents replies and send them individually ?
[15:41] <tomreyn> user42_: RFC's aren't really Ubuntu support topics, try a channel which is topically related to the IRC protocol.
[15:51] <xu-irc53w> ?
[15:52] <xu-irc53w> Hello what does bs=4M exactly do when you run dd
[15:52] <KBar> xu-irc53w, it sets both input and output block sizes to 4 megabytes.
[15:53] <xu-irc53w> Does it mean the write speed wobnt exceed 4M/S
[15:54] <KBar> no, its not about its speed
[15:54] <xu-irc53w> How do u control speed then
[15:57] <KBar> xu-irc53w, I don't think there is an option or flag for that, but I know that the sync flag to output significantly slows it down.
[15:58] <xu-irc53w> !iso
[15:58] <KBar> Because it forces a physical write after every write.
[15:59] <xu-irc53w> !dd
[15:59] <KBar> xu-irc53w, `info dd`
[15:59] <xu-irc53w> !info dd
[15:59] <KBar> From your terminal.
[16:00] <KBar> xu-irc53w, the program `dd` is part of GNU coreutils, which have a very good documentation accessible by invoking `info PROGRAM_NAME`.
[16:01] <KBar> xu-irc53w, `info dd`, `info ls`, etc. Pressing Q or Ctrl-C quits Info. <SPC> or <PgDn> moves one page down, <BS>, <DEL>, or <PgUp> moves one page up.
[16:03] <KBar> xu-irc53w, btw, if you're trying to create a bootable USB of Xubuntu, you don't need fancy options for dd. It's very light and the process should take between 5 to 10 minutes tops.
[16:04] <KBar> Just `if=/path/to/ISO of=/dev/sdX`
[16:04] <p13> status=progress is a nice one to add unless you like staring at a cursor
[16:04] <KBar> Ah, yes.
[16:06] <KBar> If you have 10 minutes of free time, you can add that flag and stare at some numbers :)
[16:06] <p13> much more entertaining
[16:07] <KBar> I don't know. I've never tried that. Usually, I just run it and forget about it.
[16:08] <p13> there is also a signal you can send it to make it spit out some status info
[16:08] <p13> i believe it's USR1
[16:08] <KBar> but yeah. for a newcomer, it is a must-have. otherwise, you might get crazy
[16:08] <KBar> and freak out
[16:10] <bebop> simple: 'dd if=nameof.iso of=/dev/sdx'
[16:11] <xu-irc53w> I found it theres actually dd for windows, i hope they work same
[16:11] <KBar> woah woah woah, dont utter that w-word here ever again
[16:12] <bebop> they don't
[16:12] <KBar> xu-irc53w, if you're on W..., try Rufus instead.
[16:13] <KBar> Seamless, easy, user-friendly.
[16:14] <xu-irc53w> www.chrysocome.net/dd
[16:16] <p13> KBar: lol i wish the community would get over this whole windows thing already
[16:17] <p13> and yeah rufus, etcher, etc.  there are many options
[16:18] <KBar> p13, I'm just kidding. :)
[16:18] <p13> i know, but it kind of scares newcomers unfortunately
[16:19] <KBar> p13, well, if anything, these arcane shell commands scare them more. :P
[16:19] <p13> lol well maybe you do have a point there
[16:22] <p13> Dno, i've been running linux as my main desktop since like 2001 or something.  Nowadays, entirely possible in _most_ cases to use linux as a regular desktop OS, without having to mess with the CLI
[16:22] <p13> used to be different lol
[16:25] <xu-irc53w> How to show package dependency without installin it
[16:26] <p13> xu-irc53w: apt show
[16:27] <xu-irc53w> Is there a demonstrate function with dpkg -i
[16:27] <p13> you mean a dry run ?
[16:28] <xu-irc53w> Smth like that, without really installing
[16:28] <p13> so you mean you have a deb file you want to install ?
[16:28] <p13> or do you want to install from repo ?
[16:29] <xu-irc53w> Yeah i want to install, i just wanna see what it goes without real installing
[16:29] <p13> yes, but is it a deb file, or do you want to install from repo?
[16:29] <xu-irc53w> Its deb from AMD
[16:30] <p13> ok, dpkg -i --dry-run
[16:30] <xu-irc53w> Ok how to use apt-show with a downloaded deb
[16:31] <p13> dpkg-deb -I
[16:31] <xu-irc53w> Thx
[16:31] <p13> no worries
[16:40] <xu-irc53w> !filesystem
[16:42] <xu-irc53w> What filesystem is mostly used now
[16:42] <p13> for general desktop use ?
[16:44] <xu-irc53w> Yes
[16:44] <p13> unless there's a specific feature you need from a particular fileystem, i'd say just stick with ext4
[16:45] <xu-irc53w> Ok how do you set back up in case for X crashes
[16:46] <p13> what do you mean?
[16:46] <xu-irc53w> How to set backup in case desktop fails
[16:47] <p13> you mean in the event your computer crashes?
[16:47] <p13> like totally crashes?
[16:47] <p13> dejadup, etc works well for your user data
[16:47] <xu-irc53w> No desktop or smth
[16:48] <ens2> so i installed ubuntu onto my laptop and after it put grub on, it doesn't give me an option to boot to windows. is there a command i can run to test how the bootloader is looking for the windows partition?
[16:49] <p13> ens2: hold shift while your computer is booting to see the grub menu
[16:49] <p13> or mash escape
[16:50] <xu-irc53w> Better set wait time for it
[16:50] <p13> xu-irc53w: which desktop environment do you run?  Gnome?  In that case, just use the backup tool that comes with ubuntu
[16:50] <ens2> yeah i got to the grub menu. it only offered the option to boot to ubuntu (no windows option)
[16:50] <p13> ens2: ah, i see.  You know where your windows partition is?
[16:51] <ens2> yeah it's on /dev/dm-3
[16:51] <p13> softraid?
[16:51] <ens2> hardware raid0
[16:51] <p13> dm-3 does not soun like hardware raid ...
[16:52] <ens2> well i set up the raid volume using the hp/intel config thing from where the bios lives. so i would hope nothing strange is going on.
[16:53] <p13> yeah that's soft raid
[16:53] <p13> see if you can run os-prober
[16:53] <ens2> for reference it's also under /dev/mapper/isw_dgdhjdjfgb_Volume1p3 -> ../dm-3
[16:54] <ens2> os-prober runs but doesn't echo any output
[16:54] <p13> yeah symlink, that's normal
[16:54] <p13> ens2: run updat-grub after os-prober
[16:55] <p13> update-grub
[16:56] <ens2> p13: https://pastebin.com/he4tqR08
[16:57] <p13> is your raid a raid1 ?
[16:58] <ens2> it is a raid0
[16:58] <KBar> ens2, you have a type. the command is `update-grub` with superuser privileges
[16:58] <KBar> you typed `updat-grub`
[16:58] <KBar> oh my bad
[16:58] <KBar> didnt see the end
[16:59] <p13> hmm raid0 softraid might be a bit problematic for this, i mean i haven't done it.  with raid1, you just point it directly to one of the disk devices, and it's fine
[16:59] <p13> hold on
[16:59] <KBar> sorry. im getting old i guess :D
[16:59] <tomreyn> ens2: what does this print?   echo -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
[17:01] <ens2> This system booted via: UEFI
[17:01] <tomreyn> ok, good. what's the physical devices you joined into this fakeraid?
[17:02] <ens2> two sandisk x400 m2 sata drives and 1 2.5 ssd that came with the laptop.
[17:03] <p13> looks like sda, sdb and sdc
[17:03] <ens2> yeah. that also. :)
[17:03] <p13> 3 disk raid0 with differing geometries.  YOLO
[17:04] <ens2> well two of them are the same at least!
[17:04]  * ens2 chuckles
[17:04] <tomreyn> and different buses
[17:04] <tomreyn> although, no , probably all sata
[17:04] <p13> yeah sdx devices, looks like sata
[17:05] <p13> looks production ready to me.  ship it
[17:05] <ens2> yeah. i thought they were nvme m2's at first but they are actually sata it seems. 3 notches on them rather than 2 on the connector is the way i was informed to tell the diff.
[17:05] <tomreyn> so the problem you are trying to solve is that os-prober doesn't find the windows bootloader?
[17:05] <ens2> tomreyn: seems to be the case indeed
[17:06] <tomreyn> have you tried mounting the ntfs?
[17:06] <p13> try your pc's boot menu.  The EFI boot entries will probably contain the windows one
[17:06] <ens2> to get to this point. i installed windows first.... then shrank the windows partition to make space for the ubuntu.. restarted to test that windows still worked and then booted into the live-cd to do the install.
[17:06] <ens2> will try mount it now
[17:07] <nabidev> https://ubottu.com/y/gl
[17:07] <ens2> oh interesting...
[17:07] <ens2> Windows is hibernated, refused to mount.
[17:08] <shadow255> sounds like fast shutdown fun
[17:08] <tomreyn> you need to configure it to shut down properly
[17:08] <ens2> The disk contains an unclean file system (0, 0).
[17:08] <p13> it needs to rest for winter k
[17:08] <p13> disable quick boot
[17:08] <ens2> haha
[17:08] <ens2> it mounted it read-only though
[17:08] <ens2> so i suppose that should be decent enough
[17:09] <ens2> but maybe os-prober picked up that error?
[17:09] <tomreyn> and while you're at it, apply the registry patch to make it accept a utc hardware clock
[17:09] <p13> it will have tried to mount it or at least get the superblock and probably got some weird non-zero exit code
[17:09] <p13> tldr: it choked on itt ... probably
[17:09] <tomreyn> possibly that's what happened. you'll need to creconfigure windows anyways, so why not try this now
[17:11] <ens2> should i try boot into it via the system F9-key boot sequence and get it to dismount it cleanly?
[17:11] <p13> yes
[17:11] <p13> disable quickboot or fastboot or whatever it's called
[17:11] <tomreyn> with this adventurous 'RAID' configuration, make sure you always have good backups for both systems
[17:11] <p13> also, yes, very much what tomreyn said
[17:12] <p13> it's more like a redundant array of imminent destruction
[17:12] <ens2> oh yeah i keep good backups indeed. this is pretty much just my gaming machine but i want to have a decent OS like ubuntu in case i want to do some serious fun work like some cuda coding or just use a nice screen for visual studio code
[17:13] <ens2> but as a gaming machine... little of value would be lost on the windows side at least.
[17:13] <ens2> anyway brb
[17:13] <p13> good luck
[17:14] <p13> i've done usb floppy raid before
[17:14] <p13> good times
[17:14] <p13> mdraid don't care
[17:19] <p13> ens2: F9 wasn't your boot menu key? :D
[17:20] <ens2> well - the good news is that i can at least get to windows by the f9-bios-boot thing. so there's a workaround...
[17:20] <ens2> and i got it to unmount cleanly so it looks like
[17:20] <ens2> https://pastebin.com/S98Zc8yH
[17:20] <ens2> but os-prober isn't giving any output still. at this point i'm happy to just get into it via the F9 menu if you guys don't feel this is worth solving
[17:20] <ens2> but if you have any bright ideas do lemme know
[17:21] <p13> os-prober is silent
[17:21] <p13> try update-grub again
[17:21] <ens2> same output as last time
[17:21] <p13> hmmm
[17:21] <p13> can you mount the partition read-write now ?
[17:22] <ens2> yep. i mounted it
[17:22] <TJ-> not been following, but os-prober is disabled by default on recent releases
[17:22] <ens2> and did echo test > test
[17:22] <p13> TJ-: oh, is there a new way?
[17:23] <ens2> this is 20.04 for reference
[17:24] <p13> is there a windows entry /etc/grub.d?
[17:25] <p13> like a windows file
[17:25] <TJ-> it's just the GRUB_ option changed the default but I can't find the changelog mention of it now, so not sure where I saw it!
[17:26] <ens2> no windows mentioend under /etc/grub.d/
[17:28] <TJ-> ahhh, no it isn't, not in releases, sorry. It's in recent upstream commits this year (I work on the upstream code a bit and saw it there!)
[17:28] <p13> hmm, you could try making the entry manually in there
[17:28] <tomreyn> is package os-prober installed, though?
[17:29] <ens2> os-prober is already the newest version (1.74ubuntu2).
[17:30] <tomreyn> oh yes, you also showed that in the paste, sorry
[17:30] <tomreyn> so i guess os-prober can't find it on the isw raid
[17:31] <ens2> yeah bit of a head scratcher
[17:31] <TJ-> can we go back a bit? ens2  you said this is an UEFI install/boot ?
[17:31] <ens2> my instinct now is to boot to grub command line and see if i can find the windows drive and do some kind of chainloader to test it works manually or something
[17:31] <ens2> TJ-: yeah
[17:31] <p13> you could add the EFI boot entry to grub
[17:32] <TJ-> ens2: in which case GRUB should NOT be involved. The motherboard firmware's own UEFI boot menu should have the Windows entry, and when you wish to start Windows you should press the hot-key at start-up that brings up the manual boot menu for the firmware
[17:32] <TJ-> ens2: use "efibootmgr -v" to assure yourself that the Windows entry is there
[17:33] <TJ-> ens2: look at the BootOrder and you'll like see Ubuntu's entry is ahead of the Windows entry so by default Ubuntu always starts, unless you tell the motherboard firmware to choose Windows
[17:34] <ens2> yep ubuntu is first in that output bootorder
[17:35] <ens2> ok then. that makes sense.
[17:35] <TJ-> ens2: and you see Windows entry too?
[17:35] <ens2> yeah, windows is there on it too as "Windows Boot Manager" which is right after Ubuntu in the boot order
[17:36] <TJ-> ens2: if you want to boot into Windows next time only, you can do "sudo efibootmgr --boot-next XXXX" where XXXX is the Windows boot order number (e.g. 0002) that avoids needing to press the firmware hotkey and select Windows from the manual boot menu
[17:37] <ens2> oh that's handy. i'll save that in a .sh
[17:37] <TJ-> ens2: efibootmgr can also be used to change the default, by setting an explicit permanent BootOrder. See "man efibotomgr" -- lots of good examples at the end
[17:38] <tomreyn> TJ-: just for me to understand: why are you saying grub should not be involved here? i mean sure, it is not needed, but it could be, or not?
[17:38] <tomreyn> i mean it could be used in addition to the uefi boot chooser
[17:38] <TJ-> tomreyn: the whole problem with trying to chainload another EFI portable executable, which is what os-prober tries to do
[17:39] <p13> well if you REALLY want to live on the edge, some google guys kexec'd into windows from linux lol
[17:40] <TJ-> The entire point of UEFI was to separate the boot-loaders from each other - os-prober was a kludge to allow multiboot when GRUB/Linux was installed last and took over the MBR
[17:40] <tomreyn> i see
[17:41] <p13> i use refind boot manager
[17:41] <p13> i have a drive with qubes, a drive with haiku and an mdraid set with ubuntu
[17:42] <p13> it keeps all of their bootloaders separate
[17:43] <p13> wish my pc just supported coreboot
[17:44] <tomreyn> p13: there's also #ubuntu-offtopic for non support Q&A
[17:44] <p13> is it OT though?  I suggested an alternative
[17:44] <TJ-> p13: UEFI keeps boot-loaders separate by design - each has its own directory under /EFI/ on the EFI system partition
[17:45] <TJ-> Ubuntu adds /EFI/ubuntu/
[17:45] <p13> yeah, and refind just allows you to drop into the efi shell, or allows you to load any efi executable.  It's kind of nice
[17:46] <ens2> thanks for the help and education on this issue folks. much appreciate.
[17:47] <p13> ens2: cool beans.  The firmware boot menu entry works i guess, but maybe check out refind if you want another solution.  https://en.wikipedia.org/wiki/REFInd
[17:50] <ens2> thanks. looks like a cool project.
[17:50] <p13> it's pretty neat.
[18:34] <veretoes> hey dudes, which lightweight ubuntu is encrypted?
[18:34] <veretoes> xubuntu maybe?
[18:35] <p13> you can have encryption on any ubuntu variant
[18:35] <p13> full disk or just your home dir?
[18:36] <veretoes> hi p13, I'd prefer full disk
[18:36] <p13> which desktop environment do you prefer?
[18:37] <veretoes> I have xubuntu installed
[18:37] <veretoes> I like it, it's ok
[18:37] <p13> you have it already installed and want to encrypt your current system?
[18:37] <veretoes> yes
[18:37] <p13> hmmm not so easy i don't think
[18:38] <p13> do you have a second disk to copy to?
[18:43] <RandomGuy21> Hey p13 how easy would it be to encrypt just the home folder on an already installed Ubuntu system
[18:44] <p13> make a new user, set up encryption, copy over
[18:45] <veretoes> nothing important on the hard disk yet, it could be formatted or whatever
[18:45] <p13> veretoes: then i suggest reinstalling
[18:45] <p13> pick set up lvm with full disk encryption
[18:48] <RandomGuy21> Cool thanks
[18:53] <veretoes> thanks
[20:33] <cientista> oi
[22:24] <Chunky_Ks> Hey all, I finally upgraded my 20.04 machine to the latest, and I'm having an infuriating issue in mate-terminal when using vi: When the mouse moves focus to another window, the terminal beeps, and vi exits insert mode. I've no idea what's happening, but I'd very much like it to stop. Can anyone suggest anything I could try?
[22:25] <p13> sounds like a GPM thing
[22:25] <p13> Some applications support the use of a mouse in the terminal.  Clicks are sent as escape codes.
[22:25] <p13> Let me have a look for you
[22:26] <Chunky_Ks> oh, huh
[22:26] <Chunky_Ks> that would align with some silliness I had with a terminal text browser, too
[22:26] <p13> when you run htop (that supports gpm), and you click somewhere, does it react ?
[22:27] <Chunky_Ks> yeah, links [the text mode browser] responds to the mouse
[22:27] <p13> yeah that's mate, though, what i mean is does htop for example react to your clicks within the terminal
[22:28] <Chunky_Ks> yep
[22:28] <Chunky_Ks> htop responds to mouse clicks
[22:29] <p13> ok cool so that works
[22:29] <p13> aka that's  not broken.  I suspect vi is getting those clicks and doesn't know what to do with them
[22:29] <p13> do you use vi or vim?
[22:29] <Chunky_Ks> I just tried my other pre-21.10 machine, and htop doesn't respond to clicks in it
[22:29] <Chunky_Ks> uh. "vi" at the terminal, lemme figure out what that actually is
[22:30] <p13> try vim
[22:30] <Chunky_Ks> currently that's vim.tiny
[22:30] <p13> ok cool
[22:30] <yakov> windows suck
[22:30] <p13> do you want to use your mouse for anything in the terminal?
[22:30] <Chunky_Ks> installing vim-not-tiny now
[22:30] <Chunky_Ks> not even a little bit :-)
[22:30] <p13> ok let's check how to disable it then
[22:31] <Chunky_Ks> ah, yeah. vim as in "sudo apt install vim" doesn't do this.
[22:31] <p13> yeah vim supports gpm
[22:32] <Chunky_Ks> nod. good call on pointingthe finger at gpm
[22:32] <p13> i recognize the behavior from occasional byobu shenanigans so it rang a bell :)
[22:32] <Chunky_Ks> nod.
[22:33] <Chunky_Ks> I've also updated alternatives to point vi at vim.basic, which also alleviates the symptoms
[22:33] <p13> vim is nicer anyway imho
[22:33] <Chunky_Ks> although personally I prefer my terminal remain ignorant of mouse altogether
[22:33] <p13> can use cursor keys lol
[22:33] <p13> hjkl is nice and all, but i'm not that cool
[22:33] <Chunky_Ks> I'm old enough and grumpy enough that I learned vi when it was "the thing Bill Joy wrote"
[22:34] <p13> well in any case, if this bothers you with anything again, you know where to look
[22:35] <p13> i would think that mate-terminal has an option in it's prefs somewhere to enable or disable mouse support
[22:37] <Chunky_Ks> hrm
[22:37] <Chunky_Ks> I don't see anything
[22:37] <Chunky_Ks> but for now I think I'm ok. at the very least, "vi" doesn't beep and drop out of insert mode when I mouse around
[22:38] <Chunky_Ks> so I'll take the victory. Thanks for your swift and excellent help!
[22:38] <p13> that would annoy me as well haha
[22:38] <p13> no worries friend
[23:30] <Guest6259> What's the best ppa to get newer kernel in older ubuntu release?


[01:34] <smoser> bdmurray: sorry to pester you always. blackboxsw and I just uploaded another cloud-init to xenial and zesty.
[01:35] <smoser>  cloud-init 17.1-18-gd4f70470-0ubuntu1~16.04.2 and cloud-init 17.1-18-gd4f70470-0ubuntu1~17.04.2
[01:35] <smoser> if you could take a look in your sru time tomorrow we'd appreciate it.  its just one *very* tiny code change compared to what was already in -proposed.
[01:36] <smoser> bug 1724354
[06:40] <mitya57> xnox: ack
[06:41] <mitya57> tsimonq2: so let's plan Qt 5.9.3 and OpenSSL 1.0 for now
[06:52] <cpaelzer> hey, if a former proposed upload failed (due to gcc7 now making it an FTBFS) is that one of the cases to buildpackage with -v <version before last> ?
[06:53] <cpaelzer> to pick up in the changes file all effective changes that will hit the archive?
[06:57] <cpaelzer> I'm rather sure it is corrct for this case, so uploading like that for now
[06:58] <cpaelzer> but feel free to let me know if you tihnk otherwise would be better (and why)
[08:38] <infinity> cpaelzer: Yep.
[08:53] <test2222> hi all, could someone have a look at this Steam issue and give me a hint where I should raise another issue please? Not sure how to help the Valve guys: https://github.com/ValveSoftware/steam-for-linux/issues/3301#issuecomment-337832330
[13:32] <Laney> :-)
[13:42] <sladen> +1
[13:42] <sladen> "next please"
[13:44]  * xnox is betting on Brisk Bustard
[13:46] <infinity> xnox: What sort of animal is a Bustard?
[13:47] <xnox> infinity, a bird
[13:47] <xnox> https://www.google.co.uk/search?q=bustard&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwjm_bPs6PzWAhXLJMAKHXUyCLEQiR4IrwE&biw=1920&bih=990
[13:47] <xnox> infinity, looks like a heron to me
[13:48]  * mitya57 hopes 18.04 won't look like 8.04 because of that
[13:48] <xnox> but i'm not into birds
[14:32] <jbicha> breezier badger
[14:32] <jbicha> edgier eft
[14:33] <jbicha> too bad it doesn't well work for dapperer
[14:34]  * Laney is going to lobby for Dabbing
[14:34] <jbicha> the first 2 LTS were birds, I was thinking it was going to be a pattern, but nope
[14:42] <Faux> Laney: <3
[14:45] <xnox> Boring Bull?
[14:55] <roadmr> hello, it looks like the mirrors serving 17.10 images don't support zsync :( https://pastebin.canonical.com/201018/
[14:56] <cjwatson> I don't think we've ever pushed the zsync files to cloudfront
[14:56] <cjwatson> it's probably a bug on the IS side that they're redirecting .iso.zsync as well as .iso
[14:57] <roadmr> cjwatson: ugh - should I report this somewhere?
[14:58] <cjwatson> roadmr: either IS on IRC or RT, I guess
[14:58] <roadmr> cjwatson: will do, thanks!
[14:58] <cjwatson> roadmr: I mean it'll be a short-lived problem, but maybe a process bug somewhere
[14:58] <roadmr> yep, I guess once the thundering herd dies down things will point where they should
[15:17] <cjwatson> (for completeness: I totally misread the pastebin, this is probably unfixable at our end)
[16:41] <Sicnus> Who updates this file?  http://changelogs.ubuntu.com/meta-release  Also,d oes Dean H. (Beret) hang out here anymore?
[16:45] <nacc> Sicnus: it will get updated
[16:45] <nacc> Beret --^
[16:45] <nacc> Sicnus: feels like you could just look at who is in the channel
[16:46] <Sicnus> Beret: oheya Dean ;)   (Trae)
[17:08] <acheronuk> now updated
[17:09] <Sicnus> yeah thanks,  ;)  Just noticed.
[17:18] <nacc> slangasek: would it be appropriate for me to SRU a MRE for php7.1 to artful, and not fix it in BB, given an intention to update to php7.2 in BB? That is, I could wait for BB to open, and do the fix there, then SRU, but I'm going to be replacing php7.1 with php7.2 in BB evenually anyways
[17:23] <slangasek> nacc: what do you mean, "and not fix it in BB"?
[17:24] <slangasek> nacc: if this is just about SRUing before BB is open, it's fine to start an SRU now and have us copy forward to BB when it opens
[17:24] <nacc> slangasek: well, yeah I guess I meant that -- as in do I need to wait for BB to open
[17:24] <nacc> slangasek: as my first plan of action for BB is to sync 7.2 and drop 7.1 anyways
[17:30] <jbicha> nacc: y'all are targeting postgresql-10 for BB, right?
[17:30] <nacc> jbicha: yeah, i believe so
[17:31] <nacc> jbicha: it should line up well
[17:31] <jbicha> Debian completed the transition so hopefully it'll be fairly smooth in BB too
[17:32] <nacc> jbicha: yep
[17:37] <nacc> slangasek: general development question; is 'devel' a valid changelog distribution only in ubuntu?
[17:39] <slangasek> nacc: yes
[17:39] <nacc> slangasek: thanks
[18:07] <bdmurray> jbicha: In addition to commenting on bug 1721626, tagging it v-failed would have been helpful.
[18:10] <jbicha> ok, not clear whether there is a regression there or not, but probably would have been better to tag it like that until it can be investigated
[18:30] <bdmurray> jbicha: Yes, because the report shows that SRU as releasable.
[20:06] <infinity> bdmurray: The bug isn't in console-setup anyway, I'm sure.
[20:07] <infinity> bdmurray: Pretty sure that's another manifestation of "sometimes plymouth --ping doesn't return".
[20:11] <bdmurray> infinity: right, I was commeting on the process
[20:13] <infinity> bdmurray: Oh yes, indeed.  I was going to v-fail it after I sorted out it was to blame.  And it clearly wasn't to blame, from a cursory view of the diff.  So, the real process failure was not removing the regression tags from the other bug.
[20:13] <infinity> bdmurray: (That said, shouldn't a regression-proposed bug be scraped by sru-report and flagged up?)
[20:16] <bdmurray> infinity: There is a bot that looks for bugs about packages from -proposed but that filters on ones reported by apport.
[20:23] <infinity> bdmurray: Ahh, well.  Yay tools.  Another argument to push for britney-driven SRU migrations this cycle.  That block-proposed tag would have actually been useful. :P
[20:43] <slangasek> infinity: yeah, was discussed at the SRU team meeting in NYC, I think we're ready to push on that this cycle
[21:10] <tsimonq2> Excuse my ignorance but will all the uploads that have been 0-day SRU'ed into Artful be automatically copied to Bubonic Baboon once it opens or will developers have to do this on a case-by-case basis?
[21:15] <LocutusOfBorg> I think the former
[21:15] <LocutusOfBorg> otherwise we will end up with big b00bs being with lower versions than artful-updates
[21:19] <tsimonq2> True, I just didn't know if Bubonic Baboon when created would copy including -updates and -security.
[21:19] <tsimonq2> (And what about -proposed?)
[21:45] <sarnold> I'd expect all but -proposed
[21:49] <tsimonq2> sarnold: But why not -proposed? Those have the potential to land and might be greater than the one in Big Bat...
[21:49] <sarnold> tsimonq2: because they might not land.. presumably there's few enough of them for real trouble
[21:51] <tsimonq2> sarnold: I guess my point is is that once they *do* land, the version will be greater than Big Bat...
[21:52] <hallyn> note on the artful desktop installer - run from inside a VM, the display always seems wrong, such that the 'continue' button for choosing a keyboard layout is off the screen, so you can't click it, have to tab over to it and guess that it is highlighted.
[22:55] <nacc> hrm, i'm getting a Hash Sum mismatch on xenial-updates from archive.ubuntu.com in a LXD container
[22:55] <sarnold> any chance ss or netstat still tells you which IP was used?
[22:55] <nacc> anyone else seeing that (i'm seing it in autopkgtest)
[22:56] <nacc> sarnold: let me see if it goes away if i refresh my local build env
[22:56] <nacc> sarnold: autopkgtest-build-lxd didn't complain, so it must be something in my autopkgtest-lxd env
[22:57] <sarnold> nacc: apt-cacher-ng? squid-deb-proxy?
[22:57] <sarnold> everyone's reported one of them corrupts files and the other one works fine..
[22:57] <nacc> yeah i think it must be acng
[23:01] <nacc> sarnold: yep, that was it
[23:02] <nacc> sorry for the noise, and thanks sarnold!
[23:02] <sarnold> nacc: did you notice if it happened to serve up a different file than the one expected? i gave up on it when I saw that once..
[23:03] <nacc> sarnold: I did not. Once i reran autopkgtest-build-lxd and used that image, it worked correctly
[23:03] <sarnold> nacc: well, at least you're moving again :)
[23:03] <nacc> sarnold: yeah :)


 I only met him a few times, but he seemed like a great guy.
[12:42] <JonathanD> He was a great guy.
[12:42] <waltman> ok, off to the train. later.
[12:43] <JonathanD> I saw him 2 weeks ago at hive open house. At the time I mentioned he should come out to north some time to hang out. He said all thsoe smart people in one room made him not feel very bright. But he was a very bright guy himself.
[12:43] <JonathanD> I'm glad I went down that day.
[13:39] <waltman> JonathanD: I kind of felt the same way when I visited hive :)
[13:41] <waltman> Oh, and if there's one thing I've learned working with electrical engineers the past couple of years, it's this: it's always the capacitors that go in HDTVs :)
[17:33] <InHisName> their MTBF is the worst of the componets used in circuits.   All these years since my schooling and only a small improvement in that.
[17:48] <waltman> For the one that they worked on in my lab, they determined it wasn't so much the capacitor itself, but rather it was a design flaw and they'd used one whose capacity was too low.
[17:48] <waltman> They replaced it with a higher capacity capacitor and it worked fine.
[17:55] <JonathanD> you can often fix TVs that way.
[17:55] <JonathanD> or LCDs


[00:08] <Unit193> infinity: Looking forward to the American election too, eh?
[01:26] <teward> for my own reference, if I update a package in the repositories that another relies on, and the package that relies on mine depends on it, how would a rebuild be issued, or what would be the most sensible way to approach that?  Hypothetically.
[01:27] <infinity> teward: Why would a rebuild be necessary?
[01:27] <infinity> teward: Are you talking an SONAME bump in a library, or similar?
[01:29] <infinity> teward: Anyhow, if there's a library transition in play, you do something like "pull-lp-source foo && cd foo-* && dch -R", enter a changelog entry like "Rebuild for the libbar transition.", and upload.
[01:30] <infinity> teward: But first, I'm curious about specifics, rather than hypotheticals.  We don't rebuild rdeps unless there's a reason.
[01:30] <teward> infinity: with regards to https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2016-June/016654.html, https://lists.ubuntu.com/archives/ubuntu-server/2016-June/007360.html, and https://lists.ubuntu.com/archives/ubuntu-server/2016-June/007361.html
[01:31] <teward> infinity: basically, it's on the discusison list - if there is a package with a .so dynamic module built against 1.10.1 and we release 1.10.2 for bugfix/security reasons, a package with the .so dynamic module would need a rebuild
[01:32] <teward> reading up on the thread may make the reasoning more clear?
[01:32] <teward> more or less to try and understand weird edge cases
[01:33] <teward> granted, i've not yet merged in Debian's dynamic module handling yet, which might be a pre-req
[01:33] <teward> rbasak: fyi ^
[01:33] <infinity> teward: Having the server ABI tied to version is madness.
[01:34] <teward> I told nginx upstream their dynamic modules approach doesn't work well in downstreams
[01:35] <infinity> teward: But, if we're stuck with that for now, then any rdeps in the archive would need a rebuild on upgrade, yes.  And they better have proper dependencies based on some nginx-signature-12345 provides or something.
[01:35] <teward> got a reply "Yeah we know, we'll work on it but it's not a short-term goal"
[01:35] <infinity> teward: It's not hard to fix.  All they need is an ABI tracker that bumps signature if and only if the ABI breaks.  Which means some rebuilds, but not on every version.
[01:35] <infinity> (This is basically the PHP approach)
[01:36] <infinity> teward: Anyhow, does nginx actually have rdeps in the archive right now?
[01:36] <teward> infinity: for now, no.  come next LTS, probably.
[01:36] <teward> or sooner, if people start putting things into Debian for third-party modules
[01:36] <infinity> So, let's solve this properly before then.  For both Debian and Ubuntu.
[01:37] <infinity> Modules need to have a specific exported ABI to depend on, so they don't have to depend on nginx (>> foo), nginx (<< bar) | nginx-foo (<< foo) ...
[01:37] <infinity> You can see how that gets ugly quickly.
[01:37] <teward> indeed
[01:37] <teward> I think this is something that should be deferred until nginx can fix things?
[01:37] <teward> because the way they've got things done, at least AIUI, there's no ABI-based handling
[01:38] <infinity> You can fake one.
[01:38] <teward> infinity: guidance on that would be appreciated
[01:38] <infinity> Remind me when it's not... Today.
[01:38] <teward> works for me :)
[01:39]  * teward looks back at the nagios page saying all his Ubuntu Server VMs are down, and figures he should probably fix them instead of worrying about nginx :P
[01:39] <teward> (at least for right now)
[01:40] <infinity> teward: As for upstream, they need to track ABI, but what they do with that information is another question.  They *could* export an ABI define somewhere, that people could test against.  Or, they could go the sane route, and promise ABI stability in a major.minor (or even just major) series.
[01:41] <infinity> teward: The latter would be much better, but it means checking for ABI breaks in upstream commits and blocking them or backing them out of people oops.
[01:41] <infinity> s/of people/if people/
[01:41] <teward> infinity: I think ABI breakage is more prone in mainline (1.9.x as an example) than 1.10.x which basically doesn't change once released
[01:41] <infinity> Well, "basically doesn't change" isn't a promise. ;)
[01:41] <teward> except for bug fixes, and I think that nginx is smart enough to make notices about it
[01:42] <teward> well, with dynamic modules being a 'new' thing with 1.9.x, 1.10.x, I think they'd put "This may break third party dynamic modules" over the lists i'm on
[01:43] <teward> and that'd prompt the need to poke rebuilds or 'fake' an ABI change
[01:43] <infinity> Not if the ABI signature checked at load time is based on the version, they won't. :P
[01:43]  * teward yawns
[01:43] <infinity> Cause, in their mind, they break modules regardless.
[01:43] <teward> infinity: I get what you're saying, i'm basically dead here.
[01:43] <infinity> Anyhow.  Another time.
[01:43] <teward> um, clarify "they"
[01:43] <teward> there's nginx upstream, Google PageSpeed upstream, and us :p
[01:44] <infinity> They, upstream.  They're not going to inform you if a change may break modules, because their "ABI" breaks on every version change anyway.
[01:44] <teward> (there's two upstreams)
[01:44] <infinity> nginx upstream. :P
[01:44] <teward> :P
[01:44] <teward> well
[01:44] <teward> i have an evil painful workflow that I currently do for a few home-grown packages which depend on others
[01:45] <teward> basically a shell script that builds one, pulls in for the build env on a separate package, and tests.
[01:45] <teward> but eh
[01:45] <infinity> We can talk more later.  I have a hot date with a shawarma.
[01:45] <teward> could potentially adapt, but CBA to bother now
[01:45] <teward> heheheh, enjoy infinity
[01:45] <teward> i'm going to go find coffee...
[01:45] <teward> and fix my servers... (I think the hypervisor powercycled...)


[00:33] <froggy1> Ubuntu 9.10 logs me out after about 30 min when I am play solitaire
[00:33] <froggy1> Ubuntu 9.04 does not
[00:34] <micahg> froggy1: is it this? bug 503428
[00:34] <ubot4> Launchpad bug 503428 in gnome-games "Ubuntu 9.1 crashes while running aisleriot solitaire (dup-of: 450832)" [Low,Incomplete] https://launchpad.net/bugs/503428
[00:34] <ubot4> Launchpad bug 450832 in ubuntu "X logout while playing aisleriot" [Undecided,New] https://launchpad.net/bugs/450832
[00:34] <froggy1> Installed on a Dell Dimension E520
[00:34] <froggy1> thanks
[02:40] <nigel_nb> hggdh, ping
[02:40] <hggdh> nigel_nb: pong
[02:40] <nigel_nb> hggdh, would be free this saturday?
[02:41] <nigel_nb> 1700 UTC
[02:41] <hggdh> nigel_nb: I do not know right now -- it is probable I will have work during the weekend, but I do not know yet when (customer decides)
[02:41] <nigel_nb> did you hear about user days?
[02:42] <hggdh> but 1700 UTC sounds pretty good in terms of *not* having work
[02:42] <hggdh> yes
[02:42] <nigel_nb> I'm taking a class on "Using Launchpad", which does include reporting bugs
[02:42] <hggdh> at 1700?
[02:42] <nigel_nb> yep
[02:42] <hggdh> I will be there. #ubuntu-classroom, I guess
[02:42] <nigel_nb> I'll be modifying an old class for reporting bugs, it would be nice to have someone around to help with answering questions
[02:43] <hggdh> yes, np. 1700UTC translates to 1100 CST. At this time, production is still running at the customer
[02:43] <hggdh> so, no upgrade possible
[02:43] <nigel_nb> oh, great :)
[02:45] <nigel_nb> so you'll be around to help with questions?
[03:01] <hggdh> yes, I will
[03:03] <hggdh> nigel_nb: ^
[03:04] <nigel_nb> hggdh, great :), sorry, was tied in user days meeting too!
[03:04] <hggdh> np.
[03:04] <hggdh> g'night to all y'all
[03:05] <nigel_nb> night hggdh  :)
[08:59] <BUGabundo_remote> morning
[13:26] <xteejx> hugday tomorrow? thought it was Tuesdays
[13:28] <pedro_> xteejx, kernel hug days are on Tuesdays
[13:28] <pedro_> the others on Thursday, that's since a couple of years
[13:28] <xteejx> pedro_: Ohh. Has it been a week since g-p-m hugday already??
[13:28] <BUGabundo_remote> ahah
[13:29] <pedro_> xteejx, yeah!, are you going to be around tomorrow? you did an awesome job and the g-p-m one ;-)
[13:49] <xteejx> Woohoo I'm on the 5 a day stats :D
[13:49] <xteejx> biggest streak hahhaa
[13:53] <kamusin> super! xteejx :)
[13:53] <xteejx> kamusin: I should be able to help tomorrow
[13:54] <kamusin> well,  I will see you there then :)
[13:56] <xteejx> :D
[14:12] <qense> Aargh! The Bug Supervisor for ubuntu-translations is subscribed to all ubuntu-translations bugs since it's the bug supervisor. This means that Ubuntu Bug Control gets all these mails as well!
[14:12] <qense> I'll try to contact dpm
[14:35] <xteejx> qense: I did wonder why ubuntu-bugcontrol emails kept containing translation stuff
[14:35] <qense> dpm has requested a maillist and when that's created it will be set as a contact address for the ubuntu-translations bug supervisor team, that should solve the problem
[14:36] <xteejx> qense: And then I assume it's a per-person option whether to sign up or not?
[14:36] <qense> The maillist will go via lists.ubuntu.com, so it's up to you to sign-up
[14:36] <xteejx> Cool
[14:37] <qense> It's policy to not create Ubuntu maillists on LP, bugcontrol is probably the exception because of the permission things
[14:38] <xteejx> I see
[15:27] <brunogirin> Hi all, I'm looking at bug #510073 which is about screen shots and was filed against Nautilus: can someone confirm whether Nautilus is the right package please?
[15:27] <ubot4> Launchpad bug 510073 in nautilus ""take screenshot" of current window doesn't work properly" [Undecided,Confirmed] https://launchpad.net/bugs/510073
[15:28] <hggdh> wow, first time I see the robot answering *before* the question!
[15:29] <mrand> hggdh: hehehe.  you're lagged.  I show 1 second.
[15:30] <hggdh> bloody wifi!
[15:30] <hggdh> brunogirin: no, Nautilus does not sounds correct
[15:31] <mrand>  gnome-utils sound right?
[15:32] <mrand> brunogirin: screen shot bugs appear to belong in gnome-utils
[15:32] <hggdh> Since the user did not specify what is being run (Gnome/XFCE), run 'alacarte', and find what programme is called by the "Take a screenshot' entry
[15:32] <hggdh> brunogirin: mrand is probably right
[15:33]  * mrand investigates alacarte.  hadn't heard of that.
[15:33] <brunogirin> mrand, hggdh: yes sounds right, searching for screen shot in the upstream tracker shows that they are mostly reported against gnome-utils
[15:34] <brunogirin> I'll change to gnome-utils and forward upstream, thanks
[15:34] <hggdh> mrand: alacarte is the Gnome menu editor. Since I never know where it will be shown in the Gnome menu, I usually run it by hand
[15:35]  * hggdh hates this idea of masking out the name of the binary in the menu
[15:35] <hggdh> brunogirin: thank you. Nice to see you here, BTW
[15:35] <mrand> hggdh: neat util.  It actually answers a question I had last night... graphical interface for changing menu icons.  Found the underlieing text config in /usr/share/applications
[15:39] <hggdh> mrand: indeed. Just be careful -- not all that is shown (usually as unselected) is meant to be shown at all; so, select carefully, so that you can unselect later on ;-)
[15:39] <hggdh> BUGabundo_remote: boa tarde
[15:39] <BUGabundo_remote> hey hggdh
[15:40] <hggdh> mrand: ah, nowadays is Preferences/Main Menu
[15:52] <brunogirin> hggdh: thanks, I thought I'd come say hello and triage some bugs while work is being slow this pm :-)
[15:52] <hggdh> brunogirin: please be our guest! We do appreciate the help :-)
[15:55] <vish> hggdh: hmm.. would it be ok if i started early on the hug day bugs?
[15:56] <hggdh> of course it is OK!
[15:56] <hggdh> vish: please do start early ;-)
[15:56] <vish> ;)
[15:58]  * vish happened to know of a two bugs listed are a dup and what the problem is :)
[16:08] <brunogirin> anybody know what package to install in Karmic as an FTP daemon? trying to reproduce an FTP related bug
[16:10] <brunogirin> ignore the previous message: user error, can't read properly :-)
[16:16] <hggdh> brunogirin: anyway, there are many different FTP servers available...
[16:20] <brunogirin> hggdh: yes I guess, I was just trying to follow the server guide that suggest using vsftpd but couldn't spell that properly when running apt-get, all sorted now
[16:45] <vish> could someone set Bug #460144 to triaged/low ?
[16:45] <ubot4> Launchpad bug 460144 in notify-osd "nm applet doesn't close notification when it is obsolete" [Undecided,Confirmed] https://launchpad.net/bugs/460144
[16:47] <bcurtiswx> vish, is it both a nm and notify-osd problem?
[16:47] <vish> bcurtiswx: both might need a change
[16:47] <vish> thats what mirco mentioned
[16:48] <bcurtiswx> ok, i will change both then. one sec
[16:49] <bcurtiswx> vish, done
[16:49] <vish> ty
[16:50] <bcurtiswx> yup, np
[17:26] <BUGabundo_remote> hggdh: #ubuntu-pt sff
[17:28] <vish> Bug #439864 can be set to triaged/wishlist
[17:28] <ubot4> Launchpad bug 439864 in network-manager-applet "No tooltips on nm-applet if not already connected to a network" [Undecided,New] https://launchpad.net/bugs/439864
[17:38] <vish> could someone set Bug #401237 and Bug #439864 to triaged/wishlist ?
[17:38] <ubot4> Launchpad bug 401237 in network-manager-applet "Feature request: network manager should be able to select multiple wireless connections for deletion" [Undecided,Confirmed] https://launchpad.net/bugs/401237
[17:38] <ubot4> Launchpad bug 439864 in network-manager-applet "No tooltips on nm-applet if not already connected to a network" [Undecided,New] https://launchpad.net/bugs/439864
[17:40] <bcurtiswx> vish, done and done
[17:40] <vish> ty
[17:49] <yofel> bug 485041 triaged
[17:49] <ubot4> Launchpad bug 485041 in network-manager-applet "Order of available wireless networks should be by strength, not alphabetical." [Wishlist,Confirmed] https://launchpad.net/bugs/485041
[17:51] <pedro_> yofel, done
[18:18] <vish> Bug #439172 and Bug #386407 triaged/wishlist bugs
[18:18] <ubot4> Launchpad bug 439172 in network-manager-applet "nm-applet icon blurry on 25+ pixel panel" [Undecided,Confirmed] https://launchpad.net/bugs/439172
[18:18] <ubot4> Launchpad bug 386407 in network-manager-applet "Applet applies 'Auto' as a prefix to all Network Names" [Low,Confirmed] https://launchpad.net/bugs/386407
[18:23] <hggdh> vish 439172 done
[18:24] <vish> ty
[18:24] <hggdh> 386407 also done
[18:40] <vish> ty , also Bug #496096 is triaged/wishlist
[18:40] <ubot4> Launchpad bug 496096 in network-manager-applet "pop up the network manager dialogue if the user is trying to connect" [Undecided,New] https://launchpad.net/bugs/496096
[18:45] <hggdh> vish, done
[18:46] <vish> ty.. heh i think i'm done for today ;) ...
[18:49]  * hggdh bows, grateful
[18:56] <yofel> bug 306878 whishlist/triaged
[18:56] <ubot4> Launchpad bug 306878 in network-manager-applet "Make it clear you've changed the /etc/network/interfaces" [Undecided,Confirmed] https://launchpad.net/bugs/306878
[18:57] <hggdh> yofel: done.
[18:57] <yofel> thx
[18:58] <hggdh> yofel, vish: when are you going to apply for bug-control?
[18:58] <vish> hehe , hggdh getting frustrated of us ? ;p
[18:58] <hggdh> :-)
[18:58] <hggdh> no, I am not, not at all. I just think you are qualified
[18:59]  * hggdh is actually *very* happy with their work
[19:00] <vish> hggdh: i was thinking of applying.. but my karma is highly misleading than my actual good bug work ;)  that is what worries me :(
[19:02] <micahg> vish: karma's basically icing on the cake, it's the cake that's really looked at ;)
[19:03] <vish> :)  ah.. well. i better send the form ... ;)
[19:03] <hggdh> vish: micahg is absolutely correct. If it were for karma, I would be way down on the list ;-)
[19:04]  * micahg didn't want to be the one to say it ;)(
[19:04] <hggdh> LOL
[19:19] <vish> hggdh / micahg  hmm , after i apply for bug control  , should i wait for an application or just send a mail to the list?
[19:19] <vish> apply in lp*
[19:19] <pedro_> vish, send your application to the bugcontrol list
[19:19] <vish> pedro_: ah , thanks
[19:20] <pedro_> vish, https://wiki.ubuntu.com/UbuntuBugControl
[19:20] <pedro_> you're welcome
[19:20] <vish> pedro_: yeah, the first line can be removed i guess > "Apply: to the Ubuntu Bug Control team and send the the Ubuntu Bug Control team application you will receive to ubuntu-bugcontrol AT lists.launchpad.net"
[19:21] <pedro_> vish, good catch, that needs to be updated
[19:21] <vish> neat
[19:37] <xteejx> pedro_: Thanks for doing bug 509866
[19:37] <ubot4> Launchpad bug 509866 in empathy "[lucid] empathy window resizes while typing in IRC" [Low,Triaged] https://launchpad.net/bugs/509866
[19:38] <pedro_> xteejx, no problem ;-)
[20:55] <xteejx> Does apport-collect work in hardy, intrepid and jaunty? If so, does it work the same as now, i.e. apport-collect -p linux ####, haven't seen anything on the wiki about this
[20:56] <yofel> it does work in jaunty afaik, not sure about hardy and intrepid
[20:57]  * yofel *hates* the launchpad bug query...
[20:57] <yofel> took me ages to find 5 bugs for my bug-control application, should have kept a list of them -.-
[20:58] <mrand> Of all the bug systems that I've used, launchpad is my least favorite.
[20:58] <mrand> Think we could move Ubuntu bugs somewhere else?  :-)
[21:00] <xteejx> hehe
[21:00] <yofel> heh, depends, does bugzilla have e-mail interaction? (the debian BTS is indeed best in this)
[21:01] <mrand> yofel, finding bugs you worked on isn't that hard though... generally: advanced search, then put your username in the "commented" field.  Probably wise to click on most of the status boxes.
[21:02] <yofel> mrand: yes, but after a year of having worked on bugs finding the ones you actually triaged yourself is a bit time consuming if the search returns ~500 hits :P
[21:02] <mrand> yeah, understood.
[21:03] <xteejx> yofel: You could've just done an advanced search
[21:03] <yofel> now that you mention it...
[21:03]  * yofel hits the head on the table
[21:03] <charlie-tca__> xteejx: hardy doesn't work the same as jaunty and karmic
[21:03] <yofel> aaargh
[21:04] <charlie-tca__> xteejx: you have to not use the -p for karmic
[21:04] <charlie-tca__> ( no "-p" for 8.10 and later)
[21:04] <xteejx> So apport-collect doesn't work at all?
[21:05] <xteejx> I have -p in lucid, and had the option in karmic....
[21:05] <yofel> -p --package works in karmic/lucid, but the manpage doesn't mention it
[21:05] <xteejx> oops
[21:06] <charlie-tca__> my mistake, that is for adding. I think it is missing in jaunty and intrepid, isn't it?
[21:06] <xteejx> I just tried it, it said its deprecated do not use it, but doesn't stop me
[21:06] <charlie-tca__> Seems like a lot of stuff is being deprecated now
[21:07] <xteejx> So H/I/J I can ask them to apport-collect the report then with no problems?
[21:07] <xteejx> Everythings being taken out, even the bloody games its silly
[21:07] <charlie-tca__> I don't think so. I think it was only karmic, wasn't it?
[21:09] <xteejx> With apport-collect you mean?
[21:09] <xteejx> I don't know.
[21:12] <charlie-tca__> yes, I think apport-collect was only in karmic, it never got backported
[21:13] <xteejx> You're kidding? I would've thought it would be, since the others are supported, and technically we still fix them/
[21:15] <yofel> apport-collect does exist in jaunty afaik, at least the kernel debugging policy has an apport-collect line for jaunty
[21:15] <xteejx> Hmm... so much for easy triage for LTS lol
[21:16] <yofel> hey, lucid will have easy triage :P
[21:16] <charlie-tca__> booting jaunty now
[21:20] <charlie-tca__> xteejx: it will work in jaunty
[21:42] <micahg> xteejx: it was one of my bugsquad meeting items that was pushed off
[21:48] <xteejx> micahg: Sorry, multitasking, what did you mean?
[21:49] <micahg> On the meeting agenda: Backporting of newest apport (if possible) to all stable releases (in  concept) -- micahg
[21:49] <xteejx> That would be a great idea if possible
[21:50] <micahg> well probably discuss it either in Feb or March
[21:50] <micahg> *we'll
[21:50] <xteejx> Is the bs meeting monthly I take it?
[21:50] <micahg> xteejx: heh, yeah
[21:50] <micahg> xteejx: agenda is here: https://wiki.ubuntu.com/BugSquad/Meeting
[21:51] <xteejx> :( What about a suggestion on the UBS mailing list?
[21:51] <xteejx> fgs my evolution keeps crashing, it's darkscreened, don't know how to report it
[21:52] <xteejx> ubuntu-bug won't do anything there's no hook for evolution, and apport won't kick in
[21:56] <xteejx> i.e. is it possible to get a backtrace for a running program?
[21:58] <micahg> xteejx: sure, https://wiki.ubuntu.com/Backtrace
[21:58] <xteejx> micahg: I don't know how to reproduce it, it happened randomly...
[21:59] <xteejx> micahg: Keep it running under gdb until it happens?
[21:59] <hggdh> xteejx: first of all, you will need a series of dbgsyms
[22:00] <xteejx> I know how to get the dbg packages and run under gdb control, but if I don't know to reproduce it, can I just leave it running under gdb's control until it happens?
[22:00] <hggdh> the easiest way to get them is by kill-11 `pidof evolution`. This will cause Evo to die on a SEGV, and apport will kick in. Go with it, but do not open a bug (stop there). Then run 'sudo apport-retrace -o trash /var/crash/evo-crash'
[22:00] <hggdh> this will make apport install all needed dbgsyms
[22:01] <hggdh> and yes, you can run it under gdb until it happens again
[22:01] <xteejx> hggdh, it's ok I know how to get the dbgsyms :)
[22:01] <xteejx> cool
[22:01] <hggdh> xteejx: there are a *LOT* of libraries used by Evo...
[22:02] <xteejx> so better off doing your way, as it will do it all?
[22:02] <hggdh> indeed
[22:02] <xteejx> ahh ok :)
[22:02] <hggdh> :-)
[22:02] <xteejx> hggdh, you're too clever :D
[22:02] <hggdh> no, I am not. I am just lazy ;-)
[22:02] <xteejx> hahaha :P
[22:05] <xteejx> hggdh: "report file does not contain one of the required fields: CoreDump Package ExecutablePath"
[22:06] <hggdh> oh. run '/usr/share/apport/apport-gtk -c <crash file>'. You must allow apport-gtk to go up to asking to find a dup
[22:06] <hggdh> only then it rewrites the crashfile with the sections
[22:06] <xteejx> so report problem, but go no further?
[22:06] <hggdh> yes
[22:06] <xteejx> ahhh
[22:07] <hggdh> it will load the thingies to the librarian, but such is life
[22:07] <xteejx> but they're not attached to anything so meh :)
[22:08] <hggdh> yeah
[22:08] <xteejx> WARNING: package <<about 20 with dbgsym>> not available
[22:09] <hggdh> no problem. The coverage is not complete, but the most important ones will be there. Hopefully.
[22:09] <xteejx> and manually select and install those i assume?
[22:10] <hggdh> if apport-retrace did not find them, they are not accessible from your sources.list (or simply do not exist)
[22:11] <hggdh> unless it is one of the major system libraries -- libglib*, for example -- usually you do not need to worry.
[22:14] <xteejx> its not working :(
[22:14] <hggdh> then, in those cases, you will usually find a .dbg (instead of a .dbgsym)
[22:14] <xteejx> ahh
[22:14] <hggdh> what is not working?
[22:14] <xteejx> It's just bitching at me
[22:16] <xteejx> gdb came up with Reading symbols from /usr/bin/evolution...Reading symbols from /usr/lib/debug/usr/bin/evolution...done.
[22:16] <xteejx> (no debugging symbols found)...done.
[22:16] <xteejx> but it seems ok now, the terminal is showing DEBUG everywhere
[22:16] <xteejx> ** (evolution:6706): DEBUG: Number of email accounts: 1
[22:16] <xteejx> ** (evolution:6706): DEBUG: EI: SHELL STARTUP
[22:16] <hggdh> yes, this is normal
[22:17] <hggdh> might even help in pinpointing the problem
[22:17] <hggdh> now, after 'r', forget the terminal (but do not close it;-) until you hit the issue
[22:18] <xteejx> of course :D
[22:18] <xteejx> hopefully it'll crash again (can't believe I said that!!)
[22:20] <hggdh> Evo is mean. Now that you are running under gdb, it will not crash.
[22:24] <xteejx> hggdh, I have a strange feeling that's exactly what's going to happen :(
[22:24] <hggdh> Not particularly surprised. Been there with Evo before.
[22:25] <xteejx> hggdh, it's that nasty code sequence " if (<user>) = you && <<active=gdb>> then $work
[22:25] <xteejx> line 666 I believe :P
[22:28] <hggdh> Evo  also uses IFD -- Improvised Fault Device, blowing out on unexpected places. Very effective, on my experience
[22:28] <xteejx> hehehehe
[22:39] <xteejx> It hasn't crashed!!!!! grrrrr
[22:40] <trijntje> Hi all, why am I not allowed to access bug 441730?
[22:40] <ubot4> trijntje: Bug 441730 on http://launchpad.net/bugs/441730 is private
[22:41] <trijntje> my bugreport is marked as a duplicate of that bug. How can I check if any information is missing if that bugreport is private?
[22:41] <micahg> trijntje: I can't access it either
[22:41] <micahg> anyone with LP superpowers?
[22:43] <hggdh> micahg: I guess will have to be at #launchpad...
[22:44] <micahg> trijntje: maybe the retracer never finished with the original bug
[22:44] <xteejx> I've had that happen before on one of mine, the auto retrace failed
[22:45] <trijntje> I dont understand, how can I see that report to make sure not information is missing?
[22:46] <micahg> trijntje: you can't unfortunately
[22:46] <xteejx> For now you can't
[22:47] <trijntje> hm, wouldnt it be better to mark the private bug as a duplicate? That way more people can contribute to solving the issue
[22:49] <xteejx> You can't because you can't access it. This sometimes happens when the retracing system crashes half way through a retrace, leaving the bug locked off
[22:50] <trijntje> xteejx, are you talking to me? Because I cant follow you :P
[22:50] <xteejx> Yes
[22:50] <xteejx> You can't mark a bug a dupe if you can't access it
[22:51] <trijntje> xteejx, no, someone else marked my bug as a duplicate of the private bug
[22:51] <xteejx> Ohhh
[22:51] <micahg> trijntje: what was your buig?
[22:51] <xteejx> Well that's silly, how do they know it's a duplicate if they can't access it??
[22:51] <hggdh> vish: you are vishoo, right?
[22:51] <xteejx> bug number?
[22:52] <trijntje> 509595
[22:52] <micahg> bug 509595
[22:52] <xteejx> bug 509595
[22:52] <ubot4> micahg: Bug 509595 on http://launchpad.net/bugs/509595 is private
[22:52] <xteejx> haha
[22:52] <ubot4> xteejx: Bug 509595 on http://launchpad.net/bugs/509595 is private
[22:52] <xteejx> micahg: joshuahoover
[22:53] <micahg> I think he's a member of the upstream project
[22:53] <micahg> my guess is the bug is private in anotehr project
[22:53] <micahg> that's why we can't see it
[22:53] <xteejx> He still wouldn't have access would he?
[22:53] <micahg> xteejx: he would since he's a member of the upstream project :)
[22:53] <xteejx> Ohh I see
[22:53] <trijntje> ubot4 is wrong, bug 509595 is not private
[22:53] <micahg> he who?
[22:53] <ubot4> trijntje: Bug 509595 on http://launchpad.net/bugs/509595 is private
[22:53] <xteejx> the ubuntuone-client is ours though...
[22:53] <micahg> trijntje: the bot's DB is a little behind
[22:54] <xteejx> Should be upstream linked or something surely
[22:54] <micahg> xteejx: the later bug was against our package, the other one is probably against the upstream project
[22:55]  * micahg thought we had a process for that now...
[22:55] <xteejx> So, an upstream tracked in LP I'm guessing, thought there was a procedure for that?
[22:55] <hggdh> it's bug 441730 that is private. ubot 4 seems to have gotten confused.
[22:55] <ubot4> hggdh: Bug 441730 on http://launchpad.net/bugs/441730 is private
[22:55] <xteejx> 509595 is also private, bug control only
[22:55] <micahg> hggdh: no, the bot's DB is a little out of date
[22:55] <hggdh> oh, OK
[22:55] <xteejx> oops, no its not, dont worry
[22:56] <xteejx> I thought we weren't supposed to dupe bugs cross-project for these reasons?
[22:57] <micahg> xteejx: no, I thought the process was to add an ubuntu task to the upstream bug
[22:57] <xteejx> that would make more sense :P
[22:57] <micahg> hggdh: maybe private upstream bugs need a different policy
[22:58] <xteejx> maybe the upstream project is private? who knows what's going on there, could be anything hehe
[23:00] <xteejx> bloody evo STILL hasnt crashed.... think I'll leave it hggdh
[23:00] <xteejx> We're definitely right about that mailicious gdb-searching code ;)
[23:02] <micahg> xteejx: no, I think the upstream bug is private, not the project
[23:02] <xteejx> Ahh ok
[23:08] <xteejx> I'm off for the night guys
[23:10] <xteejx> See you tomorrow at BugDay peeps, night :)
[23:14] <yofel> hm, the link to the progress graph on the bugday page is broken
[23:14]  * yofel goes fixing that...


[06:44] <oSoMoN> good morning desktoppers
[09:02] <seb128> goood morning desktopers!
[09:14] <oSoMoN> salut seb128
[09:14] <seb128> oSoMoN, salut! en forme ?
[09:15] <oSoMoN> ça va, et toi?
[09:20] <seb128> nickel!
[09:20] <Wimpy> Bonjour o/
[09:48] <seb128> Wimpy, salut, ça va ?
[09:50] <Wimpy> Aller bien. Mais il fait un froid glacial ici !
[09:51] <seb128> brrrrrrrr :)
[10:17] <oSoMoN> hi Wimpy !
[12:56] <kenvandine> mitya57:  hey, i got a ping for the folks at telegram asking if i can help them transition the telegram-desktop deb to a snap.  Looks like you have had a number of uploads on that, is that a package you typically look after?
[12:57] <kenvandine> the older versions do not work well and they need to be able to make sure users stay pretty current
[12:57] <kenvandine> s/for/from/
[12:57] <ogra> sounds like you want something like firefox or chromium do ? (deb2snap transition)
[13:01] <kenvandine> yup
[13:02] <kenvandine> that's exactly what they are asking for
[13:04] <jbicha> good morning
[13:06] <ogra> looks like it is an import from debian though ... there was only a singl no-change rebuild to have it pick up new Qt versions from the archive
[13:32] <mitya57> kenvandine: Hi! All my telegram-desktop uploads were just rebuilds for Qt ABI breaks :)
[13:33] <mitya57> If you need someone who needs the package well, you may try asking the maintainer of it in Debian.
[13:33] <mitya57> *who knows the package
[13:33] <kenvandine> that's fine, we wouldn't want deb2snap in debian
[13:34] <kenvandine> just making sure i wasn't going to step on anyone's toes :)
[13:35] <kenvandine> quite a few features in the version in bionic and focal aren't supported, and users just quietly miss messages, for example
[13:35] <kenvandine> and that kind of thing will continue to happen
[14:24] <ricotz> hello desktopers, could someone take a look at https://code.launchpad.net/~ricotz/ubuntu-seeds/+git/ubuntu/+merge/434778
[18:34] <bandali> good day
[18:35] <bandali> hey ricotz, so there was a new firefox point release (108.0.1) today. i'll push to both PPAs (~mozillateam's and ~ubuntu-mozilla-security's), though the sponsoring/uploading of it by security team will most likely be done after the holidays
[18:50] <ricotz> bandali, hi, great, please *only* push to ubuntu-mozilla-security ppa
[18:51] <ricotz> :\
[18:52] <ricotz> there is no need for two identicial source builds resulting in different binaries
[19:20] <ricotz> bandali, still around?
[19:59] <bandali> ricotz, hey, am around now
[19:59] <bandali> sorry i'd already pushed to the mozillateam ppa for bionic and focal :/
[20:00] <bandali> i see the builds were cancelled
[20:01] <ricotz> bandali, hey, to not conflict with the official builds in the security ppa I am adding ~mtX suffixes, but if there are foreseeable uploads to the security ppa then a binary copy of the successful builds are the best
[20:02] <ricotz> same for the thunderbird builds
[20:02] <ricotz> yeah, I cancelled them in favor the security ppa builds
[20:03] <bandali> ah ok cool cool. yeah i'll push to the security ppa for bionic and focal in a bit
[20:03] <ricotz> note that the build-deps are not an exact match between the two PPAs, so the security PPA builds are preferred
[20:04] <bandali> noted
[20:04] <ricotz> thanks! I am going to binary copy them from there when they finished :)
[20:06] <bandali> sounds good!
[20:06] <ricotz> bandali, I am wondering if there were any issues with the missing s390x builds?
[20:07] <bandali> ricotz, the desktop and security team seem to agree that the broken builds on s390x for firefox are not critical
[20:08] <bandali> but if i do manage to get my hands on a s390x vm i can try generating patch like you'd done for the other arches and see if it helps
[20:08] <ricotz> bandali, I see, noted :)
[20:09] <ricotz> I still have hope for an upstream fix to have those files properly generated on build-time :)
[20:10] <bandali> right, yeah that would be great
[21:01] <seb128> ahasenack_, hey, unsure what happened to update-notifier/bionic, didn't I fix it yesterday?
[21:02] <ahasenack_> seb128: I don't know, but the last upload again didn't have the autoconf generated files, and the build failed
[21:02] <ahasenack_> seb128: I filed a bug for it, #1999897
[21:03] <seb128> ahasenack_, where did it fail? I don't see it accepted
[21:03] <ahasenack_> seb128: I tried a build before accepting
[21:04] <ahasenack_> seb128: the one at the top (most recent), https://launchpad.net/ubuntu/bionic/+queue?queue_state=4&queue_text=update-notifier
[21:04] <ahasenack_> you can see in the diff it's removing the autoconf generated files
[21:04] <ahasenack_> I was considering uploading with that restored and accepting, but didn't get to it today
[21:05] <seb128> ahasenack_, I don't understand, I've a .upload from the right version
[21:05] <ahasenack_> seb128: do a dget https://launchpad.net/ubuntu/bionic/+upload/29992183/+files/update-notifier_<IP_ADDRESS>.dsc
[21:05] <ahasenack_> open it up
[21:06] <ahasenack_> and you will see there is only autogen.sh in the source directory
[21:06] <seb128> ahasenack_, I'm just saying I don't understand what happened
[21:06] <ahasenack_> ah
[21:06] <seb128> the content on my disk is right
[21:06] <seb128> I reuploaded...
[21:06] <seb128> it's in the queue
[21:06] <ahasenack_> seb128: the upstream bionic branch has the problem, it doesn't build in bionic
[21:06] <ahasenack_> but the bionic package, in the archive, builds
[21:06] <ahasenack_> it has the autoconf generated files
[21:07] <seb128> ahasenack_, right, I fixed manually the source yesterday to get that moving, I don't want to investigate buggy vcses at this point before holidays
[21:07] <ahasenack_> likewise :)
[21:07] <seb128> ahasenack_, the queue has a working one now
[21:07] <seb128> I just opened the source from the queue in my browser
[21:07] <ahasenack_> maybe you fixed it for one upload, then there was the wrong changes file, and that upload lost the fix?
[21:07] <seb128> it has the configure
[21:08] <seb128> yeah, dunno at this point, but if you want to wrap that before holidays the queue should be right
[21:08] <seb128> let me check xenial as well
[21:08] <ahasenack_> xenial was fine, but yeah
[21:08]  * ahasenack_ dgets
[21:08] <ahasenack_> yes!
[21:10] <seb128> ahasenack_, ah, I misread what you wrote on the bug about xenial, k, so we should be sorted out now
[21:10] <seb128> ahasenack_, thanks again for catching up the different problems and sorry for the buggy uploads
[21:10] <ahasenack_> seb128: the changes file again... ;)
[21:11] <seb128> SHRUG
[21:11] <ahasenack_> hahaha
[21:12] <seb128> ahasenack_, reupload, let's see if I managed to yet again screw something :-p
[21:12] <seb128> reuploaded I mean
[21:13] <ahasenack_> changes ok
[21:13] <ahasenack_> getting the thing
[21:13] <ahasenack_> contents ok
[21:13] <ahasenack_> phew
[21:14] <seb128> ahasenack_, THANKS :-)
[21:14] <seb128> \o/
[21:14] <ahasenack_> \o/


[10:14] <jibel_> mvo, Hello, the autoupgrade tester is reporting a failure for lucid -> lucid-updates but there's no log. http://people.canonical.com/~mvo/automatic-upgrade-testing/current-stable/
[10:22] <mvo> jibel_: thanks, I check it out, it *might* be that is just ran out of diskapce :/ unfortuantely the disk in there is really small
[10:25] <jibel> mvo, no worries, 10.04.2 being next week, I want to be sure to not miss anything.
[10:26] <jibel> mvo, regarding your question yesterday about running gui testing with xvfb, the latest version of the scripts are there https://launchpad.net/hudson-x11-guitest
[10:27] <mvo> nice
[10:27] <mvo> thanks
[10:28] <mvo> jibel: i will need to ask you for help at some point, I added a bit of mago to s-c but I did not manage to make "sendkeyevent("<pagedown>") to work in s-c. I want it to scroll the applist but for some reason no scrolling happend (I did make sure the keyboard focus is on the treeview)
[10:32] <jibel> mvo, sure. Can I have a look at the code, branch or pastebin ?
[10:35] <mvo> jibel: http://paste.ubuntu.com/564341/
[10:36] <mvo> jibel: this is against trunk, but it should not matter (that) much, I did add atk.Object.set_name to some stuff, so you may need trunk
[10:36] <mvo> jibel: but I can do a upload nowish, wanted to do that anyway (new s-c in ubuntu)
[10:38] <mvo> actually its http://paste.ubuntu.com/564343/ (there was a <tab> missing). but it does not change the behavior
[10:38] <mvo> no rush, I need to be away for some minutes anyway and then its lunchtime for me :)
[10:39] <jibel> mvo, I'll have a look and let you know.
[11:19] <mvo> jibel: just out of curisoity, when can we have the new mago in the archive? do oyu need a sponsor?
[11:20] <jibel> mvo, my packaging skills sucks :(
[11:20] <jibel> mvo, there's a pb with ldtp which doesn't recognize pagedown
[11:21] <jibel> mvo, I think the keycode sent by ldtpd might be wrong.
[11:22] <mvo> jibel: I'm happy to do the packging and sponsoring if that is the only blocker :)
[11:22] <jibel> mvo, if you use <down> instead it works.
[11:22] <mvo> sweeeeeet
[11:22] <mvo> so I just send enough downs :)
[11:22] <jibel> mvo, see http://paste.ubuntu.com/564367
[11:23] <mvo> thaks, I play with it after lunch
[11:48] <jibel_> mvo, confirmed, the keycode is wrong, in /usr/lib/pymodules/python2.7/ldtpd/keypress_actions.py I changed the keycode for pagedown/pgdown to 117 and it work. Checking other keycodes most doesn't match with what is returned by X
[11:49] <jibel_> I don't know why keycodes have those values.
[11:49] <jibel_> nagappan, ^ what do you think ?
[11:51] <jibel_> what is odd is that the keycode for <down>  doesn't match but sending <down> works as expected. Is there some xmodmap magic over here ?
[12:05] <mvo> jibel_: indeed, I can confirm that 117 fixes it. sounds something we want to distro patch then? (and send upstream)?
[12:06] <mvo> jibel_: if you have nothing pending I will upload the current mago bzr snapshot, sounds good?
[13:02] <jibel_> mvo, sounds good, there's nothing pending.
[13:03] <jibel_> mvo, I'd like to talk with nagappan before proposing a patch because I don't understand why most of the keycodes seems wrong.
[18:39] <nagappan> jibel, I created the key code based on LTFX
[18:39] <nagappan> jibel, if its incorrect, we can fix it
[20:42] <jibel> nagappan, Hi, I think it's not trivial. We need to dynamically translate from the keysym to the keycode otherwise we will fix it for european keyboards but break other keymaps :/
[20:56] <jibel> nagappan, for example the following code ldtp.generatekeyevent('azertyuiop qsdfghjklm wxcvbn') will probably output the expected string if you're using  a US keyboard, but if you're using a european keymap it generates the string "qwertyuiop asdfghjkl, zxcvb" which is obviously not what is expected. I'll submit a report.
[21:11] <hakimsheriff> HI all
[21:11] <nagappan> jibel, sure, unfortunately I have never used any other keyboard
[21:11] <nagappan> jibel, do you have some suggestion to fix it as well ?
[21:14] <jibel> nagappan, I'll investigate the xmodmap way first but I'm not sure that's really reliable. The other solution is to use directly keysym_to_keycode from xlib, but it adds a dependency on python-xlib.
[21:15] <nagappan> jibel, okay