[08:11] <DanaG> or i type 'less some doc<tab>" for "some document with spaces", and I get "less doc"
[08:11] <DanaG> oops, wrong channel.
[11:03] <troy_s> kwwii: Did I just read that?
[11:05] <troy_s> kwwii: _IF_ Fela is a go as per sabdfl, then the default GDM needs to be reconciled against it or vice versa.  I will say that trying to get the background in line with the GDM was a disaster in terms of tonal ranges, so perhaps going the other way (wallpaper tone to GDM) is prudent.
[11:07] <troy_s> kwwii: Anyways, a smidge of heads up and we can probably get a polished version out the door.  Hit me when you are in.
[17:46] <thorwil> nand: hi. what you mean, i forgot the image link?
[17:47] <thorwil> nand: it's a straight copy from the code box and indeed the image links to the idea
[17:47] <nand> thorwil: Oh. I am sure the image was not visible this morning!
[17:47] <nand> hmm....
[17:48]  * nand will have to investigate this possible bug
[19:28] <thorwil> nand: are people using the small image links? if not, or only few, maybe they should be dropped
[19:32] <nand> thorwil: It's probably too early to tell... but from the blogs I saw, it seems the bigger one is prefered
[19:32] <nand> We should wait at least one week to have a good overview, I think
[19:32] <thorwil> sure
[21:49] <troy_s> http://abduzeedo.com/10-trends-will-define-logo-design-2008
[21:49] <troy_s> kwwii: You back?


[00:19] <user1> hello
[00:20] <user1> I'm new to linux. I need to edit a pulse audio file. how do I open and edit a file as admin in Kubuntu 21.10?
[00:41] <mybalzitch> user1: will audacity do what you want?
[00:43] <user1> Crackling audio through HDMI. Need to edit pulse audio file and change a setting. none of the methods to do this that I've seen on the internet work.
[00:50] <mybalzitch> oh
[00:50] <mybalzitch> kate /file/you/need/to/edit
[01:28] <mparillo> Global theme means just that, right? I cannot have separate global themes per activity, right?
[03:51] <linhtrag> Hi
[03:51] <linhtrag>   where is this
 HXPOXW
 Hi there, I am just hoping to get some support with a simple problems I have with our desktop computer, after a recent Kubuntu install
 CS4K
 hi there, i just joined this group can my messages appear now?
[06:31] <alkisg> Isaiah, yes, your messages appear, just ask the question
[12:25] <m_tadeu> hi...I'm trying to setup samba but I can't get it to work..."smbclient -L <my_server>" returns me a NT_STATUS_HOST_UNREACHABLE...pinging it it's ok
[12:25] <m_tadeu> any ideas?
[13:33] <BluesKaj> 'Morning folks
 HI there okay thanks, So we have just installed Kubuntu with a Z590 MSI Motherboard and we cannot get the WiFi drivers to work (re @IrcsomeBot: <alkisg> Isaiah, yes, your messages appear, just ask the question)
[14:16] <oerheks> What wifi chip exactly? lspci will show the devices, paste that one line here please
[14:17] <oerheks> and did you update the motherboard bios first?
[14:17] <alkisg> Isaiah, what's the output of: lsusb | nc termbin.com 9999
[14:19] <oerheks> Z590-ACE gives Intel® Wi-Fi 6E AX210 ..
[14:23] <oerheks> and on what kubuntu version?
[14:23] <alkisg> Eh, he'll probably answer in another 8 hours :D
 Hi sorry my internet is very slow here
 updating the motherboard BIOS do you mean a firmware update from the MSI website?
[14:29] <oerheks> yes.
 I want able to as MSI does not supply firmware update for non windows OS systems
 okay I will get that now (re @IrcsomeBot: <oerheks> What wifi chip exactly? lspci will show the devices, paste that one line here please)
 Hi it's very hard to paste the output (re @IrcsomeBot: <oerheks> What wifi chip exactly? lspci will show the devices, paste that one line here please)
[14:39] <oerheks> look at that line, and give us the 8 digit hex number ;  xxxx:yyyy
 I can't post photos and there are lots of line after I typed that command
 I typed lspci
 It says NC: getaddrinfo for host "termbin.com" port 9999: temporary failure in name resolution
 I am running kubuntu 20.04 with kernel version 5.11.0-40-generic
 I typed <oerheks> into the terminal it says nothing (re @IrcsomeBot: <oerheks> look at that line, and give us the 8 digit hex number ;  xxxx:yyyy)
 When I plug in a network card it works great but when I remove it the wifi in the motherboard won't work
 Just to confirm the motherboard has a built in WIFI card which does not work. It seems I may need to wait for a new kernel update possibly?
[15:03] <alkisg> Isaiah, plug the ethernet cable so that the nc termbin command works, so that you can give us the output
[15:03] <alkisg> (lspci; lsusb -nn) | nc termbin.com 9999
[15:05] <oerheks> !info backport-iwlwifi-dkms
 Sorry for my delay I was trying to move the computer to where the router is but its very difficult. I can connect the other network card would that help (re @IrcsomeBot: <alkisg> Isaiah, plug the ethernet cable so that the nc termbin command works, so that you can give us the output)
 I beleive I tried this yesterday evening with an ubuntu tutorial with no success. (re @IrcsomeBot: <ubottu> backport-iwlwifi-dkms (9340-0ubuntu4, impish): iwlwifi driver backport in DKMS format. In component universe, is optional. Built by backport-iwlwifi-dkms. Size 1,676 kB / 10,137 kB)
 According to this article it mentions that Ubuntu 21.04 is the only version which can support Z590-E Asus board which is very similar to my board
 https://askubuntu.com/questions/1335033/ubuntu-doesnt-recognize-wifi-on-asus-rog-strix-z590-e-motherboard
 So would that mean I should have installed more newer version of Kubuntu?
[15:51] <oerheks> Isaiah, install backport-iwlwifi-dkms ( make sure Universe is enabled in updates)  and reboot
 okay thanks very much, can you please tell me the command again and how to check universe is enabled ?
 okay thanks very much, can you please tell me the command again and how to check universe is enabled ? (re @IrcsomeBot: <oerheks> Isaiah, install backport-iwlwifi-dkms ( make sure Universe is enabled in updates)  and reboot)
[16:32] <oerheks> go into software > settings
[16:32] <oerheks> or comandline:  sudo add-apt-repository universe
[16:33] <oerheks> and run sudo apt update beforeinstalling
 Okay thanks so much ! and also just to check to install the backport I type: sudo apt install backport-iwlwifi-dkms (re @IrcsomeBot: <oerheks> go into software > settings)
 Okay I ran the install and it says " error ! Module backport-iwlwifi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates it should not be built. Skipped". (re @IrcsomeBot: <oerheks> Isaiah, install backport-iwlwifi-dkms ( make sure Universe is enabled in updates)  and reboot)
 Not sure what to do now perhaps there is a later kernel on the later release kubuntu? I am running kubuntu 20.04.3 LTS
 0202
 xmfn
 Hello. I have trouble with KDE. Sometimes my desktop, Krunner and etc freezes, but other apps like telegram, browser, webstorm, etc are running. My system:
 kubuntu 21.10
 KDE plasma version: 5.22.5
 KDE framework version: 5.86.0
 QT version: 5.15.2
 KErnel version: 5.13.0-21-generic (64-bit)
 Hello. I have trouble with KDE. Sometimes my desktop, Krunner and etc freezes, but other apps like telegram, browser, webstorm, etc are running. My system:
 kubuntu 21.10
 KDE plasma version: 5.22.5
 KDE framework version: 5.86.0
 QT version: 5.15.2
 KErnel version: 5.13.0-21-generic (64-bit)
[19:22] <mybalzitch> lol
[19:26] <tomreyn> !paste | Uchihanoureii
 Hello. I have trouble with KDE. Sometimes my desktop, Krunner and etc freezes, but other apps like telegram, browser, webstorm, etc are running. My system:
 kubuntu 21.10
 KDE plasma version: 5.22.5
 KDE framework version: 5.86.0
 QT version: 5.15.2
 KErnel version: 5.13.0-21-generic (64-bit)
[19:30] <oerheks> Uchihanoureii see that !paste factoid, you make the servers go wild


[08:11] <guiverc> installation question:  in which package is the `rsync -aHAXr --filter=-x trusted.overlay.* --exclude /proc --e-gress /tmp ..` (or whatever) that writes the ISO to disk during installation found   (if anyone knows off the top of their head)
 That would be in the Calamares code. Calamares takes the squashfs and copies it to the destination.
[08:35] <guiverc> thanks kc2bez ; i thought i found it in calamares-settings-lubuntu/calamares-log-helper but then what i found didn't match..
[08:37] <guiverc> yeah /calamares-<IP_ADDRESS>/src/modules/unpackfs looks a little better so thanks :)
[08:38] <kc2bez> Sure thing.


[00:21] <bluesabre> Unit193: very nice :D
[00:21] <bluesabre> maybe I'll work on hacking mpris into it next
[00:22] <Unit193> Yer alive!  I poked before but you just made me sad.
[00:22] <bluesabre> :(
[00:27] <bluesabre> Unit193: which poke?
[00:28] <Unit193> bluesabre: greeter-settings
[00:28] <bluesabre> that one
[00:28] <bluesabre> I still have those tabs open, so yay
[00:28] <Unit193> \o/
[00:28] <Unit193> krytarik would like to comment about one of them.
[00:29] <Unit193> I think I poked you otherwise too...
[00:29] <krytarik> I don't, but in fact I think I did already earlier.
[00:30] <bluesabre> Seem to have lost that one
[00:31] <krytarik> And by earlier I mean looooong ago. :P
[00:31] <Unit193> krytarik: I think I'd use 'case' there..
[00:31] <Unit193> krytarik: No, gtk-greeter about missing an arg.
[00:31] <Unit193> Eg, --socket foo
[00:32] <krytarik> Yes.
[00:36] <Unit193> krytarik: If we don't make a suggestion soon, we'll lose him again.
[00:44] <bluesabre> Go for it
[00:45] <bluesabre> an MP would be even better :D
[00:45] <Unit193> Hmm...Best to just merge the one from Debian then. :P
[00:53] <Unit193> bluesabre: Thanks!
[00:54] <bluesabre> Unit193: no problem, let me know if there is anything else I should review... I know I have two SRUs to get started on soon
[00:54] <Unit193> Which ones?
[00:56] <bluesabre> weather plugin and thunar... I think
[01:03] <Unit193> bluesabre: TBH, I think it makes more sense to trim the pkexec wrapper down to just like the synaptic one..
[01:04] <bluesabre> Unit193: want to paste that? I don't use synaptic :D
[01:04] <Unit193> #!/bin/sh
[01:04] <Unit193> pkexec "/usr/sbin/synaptic" "$@"
[01:04] <Unit193> bluesabre: TBH, I don't either.
[01:10] <bluesabre> Unit193: That's something a synaptic user would say
[01:11] <Unit193> s/synaptic/apt/ :D
[01:11] <Unit193> There's only one thing it can do that apt can't now.
[01:15] <bluesabre> Which is?
[01:15] <Unit193> List by origin.
[01:18] <bluesabre> Handy
[02:23] <Unit193> Waaaait a minute...
[02:24] <Unit193> http://paste.openstack.org/show/Ukq7eExmIXP4BZamv4jN/ soo, left the actual ui file unpatched and only hit the pot?
[02:39] <Unit193> (proposal submitted.)
[06:46] <flocculant> Unit193: re pkexec I assume you mean change the mousepad thunar ones to look the same?
[06:46] <Unit193> No.
[06:46] <flocculant> what do you mean then?
[06:47] <Unit193> http://bazaar.launchpad.net/~lightdm-gtk-greeter-team/lightdm-gtk-greeter-settings/trunk/view/head:/bin/lightdm-gtk-greeter-settings-pkexec
[06:48] <flocculant> oh right - ok :)
[09:44] <bluesabre> Unit193: thanks, and fixed it in other spots too
[09:48] <Unit193> Hrm, I thought I saw those, then I forgot 'em. :(


  But.. it looks like I can set the border on the GtkImage of the close button and that works better.  Is that OK?
[09:01] <seb128> hey willcooke
[09:01] <seb128> how are you?
[09:01] <didrocks> morning willcooke
[09:02] <seb128> willcooke, larsu was around until like 10 minutes ago, he went to the gym
[09:02] <willcooke> aint no thing, it can wait
[09:02] <seb128> willcooke, did you copy what the gedit-adwaita is doing?
[09:02] <seb128> I didn't pay attention to the borders much but that looked better to me that the non themed ones
[09:02] <seb128> well the ones in the sidebar documents list at least
[09:02] <seb128> you might be speaking of tabs or something else
[09:02] <Laney> morning
[09:03] <willcooke> seb128, yeah got that all sorted, just trying to match the theme as closely as possible from the old one specifically when you hover over a close button you get a border
[09:04] <seb128> k
[09:04] <seb128> hey Laney! how are you? getting over the cold?
[09:04] <willcooke> seb128, hrm, but good point - adawita is doing what I want actually
[09:05] <willcooke> seb128, also I've finished copying the bits over from Adwaita gedit to our theme, just need to get these close buttons done and we're good to go
[09:05] <seb128> \o/
[09:05] <seb128> let me know when you have that up
[09:05] <willcooke> will do
[09:05] <seb128> I can test it there and then start on the landing
[09:06] <Trevinho> seb128: so, so...
[09:06] <Trevinho> Hey didrocks
[09:06] <seb128> Trevinho, sooooo
[09:07] <Laney> seb128: it is more of a cough now
[09:07] <Laney> sooooooooooo I hope that is progress?!?!?!
[09:07] <didrocks> Laney: happy that you start feeling better! :)
[09:09] <willcooke> Laney, can you remind me what, if anything, we decided about libinput?
[09:10] <Laney> willcooke: that we thought tjaalton was handling it...
[09:10] <Laney> or would
[09:11] <willcooke> ah yes, and he said something along the lines of "it's pretty much necessary for the future, so we should try and get it in for 16.04"
[09:11] <willcooke> $customer asking about whether libinput would be in 16.04
[09:12] <didrocks> $customer is a customer with some dollars? :)
[09:13] <willcooke> :)
[09:14] <Laney> I'm sure that either way the OEM build would be able to have it
[09:14]  * Laney is using libinput driver already
[09:14] <tjaalton> xserver-xorg-input-libinput is in the archive, but in universe as nothing depends on it yet
[09:14] <Laney> hey tjaalton
[09:14] <willcooke> ah cool, thanks tjaalton
[09:14] <tjaalton> once the unity input config capplet supports it we can include it via xserver-input-all
[09:15] <willcooke> and then it would be available to anything that wanted to use it?
[09:15] <seb128> tjaalton, it replaces other drivers right?
[09:15] <seb128> are Debian/Fedora using it?
[09:15] <willcooke> Trevinho, or maybe seb128 can you comment on input config capplet ^^ ?
[09:15] <seb128> would we loose any feature by switching?
[09:15] <tjaalton> seb128: fedora is
[09:16] <tjaalton> no
[09:16] <tjaalton> it doesn't support wacom yet, but that's coming in libinput itself
[09:16] <tjaalton> but it would replace evdev and synaptics as a start
[09:16] <seb128> willcooke, well basically it means updating u-s-d/u-c-c code by importing what GNOME did, our versions are quite different so it's non trivial but still doable
[09:17] <seb128> tjaalton, how risky is the change?
[09:17] <seb128> like is likely to make trackpads not work correctly?
[09:17] <tjaalton> seb128: I think it's an overall improvement
[09:17] <seb128> or edge scrolling or some things work differently?
[09:17] <tjaalton> all work
[09:17] <seb128> k
[09:17] <seb128> do you have any cycle to backport the libinput conversion in u-s-d/u-c-c?
[09:18] <seb128> or is that something we should look at
[09:18] <seb128> I've that on my todolist but that list is long
[09:18] <tjaalton> I'm working on lts-wily backports atm
[09:18] <seb128> I'm also trying to backport the new wacom code from g-s-d, same story
[09:19] <tjaalton> the u-s-d/u-s-c fork is for good?
[09:20] <seb128> yes
[09:20] <seb128> well, for good ... at least for the coming LTS
[09:20] <seb128> I doubt it's relevant in unity8
[09:21] <tjaalton> no way to configure things?-)
[09:21] <seb128> in unity8?
[09:21] <Laney> there's a new settings app there
[09:21] <seb128> let's keep that for another day
[09:21] <tjaalton> hehe
[09:21] <tjaalton> ok
[09:21] <seb128> but yeah, there is ubuntu-system-settings
[09:21] <seb128> but it's limited, though there is ongoing work to make it fit for convergence
[09:22] <seb128> but that's not really important for the LTS/libinput discussion
[09:22] <tjaalton> right
[09:22] <tjaalton> anyway, I think debian would be ripe to do the switch, need to ask other folks on the team
[09:23] <tjaalton> they don't have unity to worry about :)
[09:23] <seb128> GNOME was talking about dropping the non-libinput code
[09:23] <seb128> so Debian is eventually going to follow by just updating
[09:26] <tjaalton> ok
[09:31] <seb128> tjaalton, what happens today if we start using libinput?
[09:31] <seb128> reading https://bugzilla.gnome.org/show_bug.cgi?id=740604 and looking to git, I'm not even sure we need u-s-d/u-c-c changes?
[09:32] <seb128> ah, it says they decided against the wrapper
[09:32] <seb128> so GNOME moved the handling in g-s
[09:32] <tjaalton> so it seems
[09:33] <tjaalton> I guess migrating now in xenial wouldn't be too dramatic
[09:33] <tjaalton> but at least all the forcepads I have need libinput, synaptics just doesn't work
[09:34] <tjaalton> or needs too much pressure to move the cursor
[09:34] <tjaalton> but the kernel driver is lacking something so right-button emulation isn't working, making forcepads still somewhat crippled..
[09:34] <tjaalton> but that's not related to the migration
[09:35] <seb128> yeah
[09:35] <pitti> hey Laney, how are you?
[09:36]  * pitti missed you coming "in"
[09:36] <pitti> Laney: ignore the autopkgtest mass failure emails, dealt with (that was me breaking debhelper)
[09:40] <seb128> tjaalton, willcooke, I think we would need to update u-s-d/u-c-c to use the new api/property for libinput (not idea what changed but reading the GNOME bug it seems the way to change configs probably changed)
[09:40] <willcooke> and then for synaptics, we just keep using the old drivers?
[09:41] <tjaalton> no libinput replaces the synaptics driver
[09:42] <willcooke> I R Confused.  So with libinput people with synaptics touchpads would have a bad time?
[09:42] <tjaalton> no
[09:43] <tjaalton> libinput replaces evdev and synaptics
[09:43] <willcooke> ohh
[09:43] <willcooke> so people with forcepads would be happier with libinput
[09:43] <willcooke> and everyone else probably wouldn't notice
[09:43] <Laney> would you remove those drivers?
[09:43] <tjaalton> probably
[09:43] <tjaalton> or my hw is just funky so that synaptics doesn't work well
[09:43] <Laney> or have code to handle both?
[09:44] <willcooke> how do we turn "probably" in to something more concrete that we can rely on for an LTS?  Is it a case of spending more time looking in to it?
[09:44] <tjaalton> no -evdev and -synaptics would still be around for some time, but probably gone before release
[09:45] <tjaalton> more folks using it. I know there have been issues with pointer acceleration code, but that's fixed by now I think
[09:45] <seb128> ok, so let's supposed we drop evdev and synaptics
[09:45] <tjaalton> libinput 1.2 will be released soon
[09:45] <seb128> and put libinput
[09:45] <seb128> what happens if we do no other change
[09:45] <seb128> if I go to u-c-c and change e.g edge scrolling
[09:45] <seb128> would that setting work?
[09:46] <tjaalton> not sure it would even show that
[09:46] <seb128> so we would regress functionnalities?
[09:46] <tjaalton> on the config side yes
[09:47] <tjaalton> two-finger scroll still works :)
[09:47] <tjaalton> at least here it just shows primary-button and double-click settings
[09:47] <tjaalton> nothing else
[09:48] <seb128> so my touchpad has edge scrolling and I like that better than 2 fingers scrolling
[09:48] <seb128> with libinput I wouldn't be able to use edge scrolling anymore?
[09:48] <tjaalton> dunno
[09:48] <tjaalton> it's easy to test, just install the driver
[09:49] <tjaalton> you can configure it with xinput
[09:51] <Laney> oh, missed pitti's hello - hi!
[09:51] <davmor2> laney he was in stealth greeting mode
[09:52] <seb128> tjaalton, seems the current code does XChangeDeviceProperty() calls to change settings
[09:52] <seb128> andXGetDeviceProperty()
[09:52] <seb128>         rc = XGetDeviceProperty (GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()), xdevice,
[09:52] <seb128>                                  prop, 0, 2, False,
[09:52] <seb128>                                  XA_INTEGER, &act_type, &act_format, &nitems,
[09:52] <seb128>                                  &bytes_after, &data);
[09:53] <seb128> willcooke, so I guess it's currently not in our backlog, we don't have anyone understand the pro/con and the work needed
[09:53] <seb128> if that's something we should work on we need to create an item for it and investigate those
[09:54] <seb128> so not on the path to happen unless we decide it should
[09:54] <seb128> tjaalton, ^
[09:55] <tjaalton> ok
[09:57] <willcooke> thanks seb128 tjaalton
[09:57] <willcooke> yeah, sounds like there is a lot of work to be done before we know
[09:57] <willcooke> maybe I can find another team to look in to that
[09:57] <seb128> I'm unsure about "lot"
[09:58] <willcooke> non-trivial then :)
[09:58] <seb128> right
[09:58] <seb128> brb, restarting without evdev/synaptic drivers and with libinput one, just to see
[09:59] <tjaalton> you don't need to remove anything btw
[09:59] <andyrock> willcooke: I need 5 more minutes
[09:59] <seb128> it might confuse u-c-c to think it can configure things where it can't
[10:00] <willcooke> andyrock, oki no worries - ping when you are ready and we can join the HO  ( <--- Trevinho, hikiko, seb128)
[10:01] <andyrock> waiting for the lecture break but the the teacher is kind of excited maximizing a log likelihood :D
[10:01] <Trevinho> willcooke: I'm in
[10:02] <willcooke> andyrock, :)
[10:04] <hikiko> willcooke, sec
[10:04] <hikiko> sorry
[10:06] <willcooke> andyrock, we're in the HO and we will get started
[10:07] <seb128> willcooke, tjaalton, so installed libinput, removed evdev/synaptic, restarted session, my edge scrolling isn't working anymore
[10:07] <seb128> the touchpad section of the settings also vanished
[10:07] <seb128> no "tap to click"
[10:07] <seb128> or "edge scrolling"
[10:07] <seb128> so yeah, needs porting to the new api
[10:08] <tjaalton> seb128: you don't need to remove anything, libinput just overrides the xorg.conf.d snippets evdev/synaptics provide
[10:08] <seb128> tjaalton, right, I just wanted to be a clean state to not confused the UI controls
[10:08] <seb128> to be on*
[10:08] <seb128> unsure what they check
[10:08] <tjaalton> sure
[10:09] <Laney> These have to be updated to look at the libinput xinput properties no?
[10:09] <andyrock> willcooke: looking for the link
[10:10] <Laney> Currently it looks for "Synaptics foo" for many foo
[10:10] <Laney> but xinput list-props x shows a lot of "libinput foo"
[10:13] <seb128> Laney, right, that's basically what I was saying/confirming
[10:13] <seb128> needs code change
[10:13] <seb128> and GNOME didn't do those for us since they moved the handling to g-s
[10:13] <Laney> they put it in gnome-screenshot?!?!?!?!?!?!?!?
[10:13] <seb128> :-)
[10:20] <seb128> libinput edge scrolling sucks :-(
[10:20] <seb128> I enabled it with "xinput set-prop 16 "libinput Scroll Method Enabled" 0 1 0"
[10:20] <seb128> but it's practically impossible to use on my latitude
[10:22] <tjaalton> how?
[10:23] <seb128> dunno, I've to have my finger really close from the border and press more than before
[10:23] <seb128> and it only detects it as a scrolling half of the time
[10:23] <seb128> http://who-t.blogspot.nl/2015/03/why-libinput-doesnt-support-edge.html
[10:23] <seb128> that is deprecated but it explained by libinput was not doing edgescrolling/how it conflicts with other features
[10:24] <tjaalton> yep
[10:24] <seb128> so maybe they detection/logic is different from what older drivers are doing
[10:24] <seb128> in any case it's harder to use on my machine
[10:25] <tjaalton> could just be a bug
[10:25] <seb128> yeah
[10:25] <tjaalton> seems fine on mine
[10:25] <seb128> well, it just confirms that it's not a trivial no-change swap
[10:25] <seb128> we are introducing new code and different behaviours
[10:25] <seb128> and different set of bugs
[10:25] <seb128> anyway, enough playing with that
[10:26] <seb128> it's enough to confirm that changing involves some wokr
[10:26] <willcooke> thanks a lot seb128, tjaalton, Laney
[10:26] <seb128> going to let willcooke&other managers decide if it's high enough that we need to budget cycles for it
[10:26] <seb128> willcooke, yw!
[10:26] <seb128> brb, rebooting
[10:27] <tjaalton> well, perhaps keep evdev/synaptics around and make it easy to switch back
[10:27] <Laney> who's going to do the u-c-c/u-s-d work?
[10:28] <willcooke> no one right now
[10:31] <Laney> I mean in theory
[10:31] <seb128> back
[10:32] <Laney> feel like it's sort of being glossed over but that is tough
[10:32] <Laney> yo
[10:32] <seb128> I missed some context I guess
[10:32] <Laney> I tried edge and it seems okay here, hate that mode though :P
[10:32] <willcooke> well, I imagine someone in our team would work on it
[10:32] <willcooke> seb128, <Laney> who's going to do the u-c-c/u-s-d work?
[10:34] <seb128> Laney, that was my comment about "up to the managers to decide how much of a priority it is and what resources get allocated to it"
[10:38] <Laney> ok
[10:39] <Laney> if we do no work then OEMs can still include it and preset their defaults in xorg.conf snippets btw, just users won't be able to configure it with a gui
[10:39] <seb128> right
[10:45] <willcooke> Laney, yeah good point.  If they do want it on in their images, I'm hoping that we can get them to commit to some of the work as well
[10:46] <Laney> willcooke: yeah - the feature tests mean that we don't expose any *broken* UI
[10:46] <Laney> - g_bit_nth_lsf@Base 2.12.0
[10:46] <Laney> - g_bit_nth_msf@Base 2.12.0
[10:46] <Laney> - g_bit_storage@Base 2.12.0
[10:46] <Laney> +#MISSING: 2.47.2-1# g_bit_nth_lsf@Base 2.12.0
[10:46] <Laney> +#MISSING: 2.47.2-1# g_bit_nth_msf@Base 2.12.0
[10:46] <Laney> +#MISSING: 2.47.2-1# g_bit_storage@Base 2.12.0
[10:46] <Laney> dddddddddddddddddddddddddddddddessssssssssrrrrrrrrrrtttttttttttt
[10:46] <seb128> desssrttt
[10:46] <larsu> desrt!
[10:47] <Laney> there's some weird shit going on around inline functions in this release
[10:47] <larsu> willcooke: I guess it should be ok. in general we try to avoid setting things on widget names directly
[10:47] <larsu> and use classes instead
[10:47] <Laney> larsu!!!!
[10:47] <larsu> morning all that I have missed
[10:47] <larsu> hi Laney :)
[10:47] <Laney> been @ gym?
[10:47] <larsu> ya. and going to lunch now
[10:47] <Laney> haha
[10:47] <seb128> larsu, enjoy!
[10:47] <Laney> tough day
[10:47]  * larsu will have to work more in the afternoon/evening today :)
[10:47] <larsu> thanks!
[10:47] <willcooke> larsu, got it, thanks.  Had a look at how Adawaita was doing it and saw that was the correct way, and actually, I just got it sorted
[10:48] <larsu> willcooke: very cool :)
[10:48]  * larsu thinks willcooke is shaping up to be a good theme maintainer
[10:48] <willcooke> it seems though that -gtk-gradient borders can't have radiused edges
[10:48] <larsu> hm really?
[10:48] <willcooke> I'm verrrrry slow
[10:48] <larsu> if css can do it, gtk should be able to as well
[10:48] <willcooke> yeah, at least border-radius doesn't have an effect
[10:48] <larsu> bug?
[10:48] <willcooke> maybe I need to slice them to make it work
[10:49] <willcooke> but that's too hard for me
[10:49] <larsu> :)
[10:49] <larsu> anyway - to late for my lunch date. see you in a bit
[10:49] <willcooke> l8r#
[10:57] <willcooke> background-color: rgb(255,0,0); is the CSS equivalent of print "XXXXX I am here!"
[10:57]  * willcooke <-- l33t hax0r
[10:58] <Laney> * { color: red; background-color: limegreen; } // IS THIS THING EVEN RUNNING?
[10:58] <willcooke> :)
[10:59]  * Laney has done this kind of thing before
[11:00] <Laney> when fixing o-s issues back in the day
[11:02] <seb128> Trevinho, btw did you meant to ask about something earlier with your "so, so..."?
[11:03] <Trevinho> seb128: no, as few mins before you asked how I was... :)
[11:03] <seb128> Trevinho, oh, sorry, I didn't read that as a reply, rather than as an opinion to a topic to discuss
[11:03]  * seb128 hugs Trevinho
[11:04] <Trevinho> :-)
[11:10] <seb128> Trevinho, did you find a way to deal with the matching issue with nautilus? btw did you see my comment about gedit/are you looking at that one as well?
[11:11] <willcooke> seb128, I want to check a couple of bits of styling before commiting these changes.  Can I just add a "padding: 10px" (or whatever it was in to gtk-widgets.css for testing?
[11:11] <willcooke> oh, this is for the file dialog
[11:12] <willcooke> not the normal file browser, the other one
[11:12] <seb128> sure, why not?
[11:12] <seb128> the sidepane widget is shared between nautilus and file-selector
[11:12] <seb128> I'm unsure what you are asking?
[11:13] <seb128> https://code.launchpad.net/~willcooke/ubuntu-themes/fix1515557/+merge/278423 ?
[11:13] <Trevinho> seb128: for nautilus https://code.launchpad.net/~3v1n0/bamf/safer-pid-desktop-registration/+merge/278461
[11:13] <seb128> cool
[11:13] <Trevinho> seb128: for gedit, I don't know... As I said yesterday we already use the _GTK_APPLICATION_ID (thanks to larsu's work) to use it as desktop-id... So not sure why it doesn't work
[11:14] <Trevinho> seb128: I didn't see the issue btw (yet)
[11:15] <willcooke> seb128, ah, this is the one I meant:  https://bugzilla.gnome.org/show_bug.cgi?id=758585
[11:16] <willcooke> I'll just hack that fix in so I can test gedit
[11:16] <willcooke> and make sure I don't commit it
[11:16] <seb128> willcooke, you can also upgrade gedit, that fix landed in xenial yesterday
[11:17] <willcooke> ah, even better, thanks seb128
[11:17] <seb128> yw
[11:20] <seb128> Trevinho, with gedit the issue is that if I dnd gedit from the dash to the launcher I gedit a gedit.desktop added to my launcher
[11:21] <seb128> but if I start gedit from a command line I get
[11:21] <seb128> _GTK_APPLICATION_ID(UTF8_STRING) = "org.gnome.gedit"
[11:22] <seb128> which leads to a new icon in the launcher
[11:22] <seb128> same if I open a document from gedit
[11:22] <seb128> ups
[11:22] <seb128> gedit->nautilus
[11:24] <Laney> seb128: could those theme tweaks go to the 3.18 branch too?
[11:24] <Laney> oh they did
[11:24] <Laney> nice ;)
[11:24] <seb128> righnt
[11:24]  * Laney needed to pull
[11:40] <seb128> willcooke, Laney, https://bugs.launchpad.net/gtk/+bug/1519778 just for info (corresponding bugzilla bug filed as well)
[11:41] <willcooke> thx seb128
[11:41] <seb128> yw
[11:43] <willcooke> hrm, my theme changes are working.  Back to the drawing board...
[11:44] <seb128> not working?
[11:44] <willcooke> my selectors arent matching
[11:44] <didrocks> seb128: I guess will feels that working is wrong :)
[11:44] <willcooke> oh
[11:44] <willcooke> *are not
[11:44] <seb128> charles, hey, any chance you could have a look to https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1261191 ? it seems like a good one to fix for the LTS
[11:44] <didrocks> "what, this is working, let's revert it" :)
[11:45] <seb128> hehe
[12:12]  * Laney switches on bbc parliament
[12:18] <Trevinho> Laney: what's happening?
[12:18] <davmor2> Sweet5hark: do you have a screenshot of what the icons in LO should look like on Ubuntu at all, I think I still see the gnome ones in kvm on the daily in live session on first start up but would like to be sure
[12:19] <Laney> Trevinho: a bit of political theatre, some budget cuts to be announced
[12:19] <Laney> seb128: thx for the bug
[12:23]  * Laney screams
[12:23] <Laney> sun just started reflecting off a window opposite
[12:23]  * Laney goes blind
[12:23] <davmor2> Laney: what is this sun of which you speak
[12:24] <Laney> you don't want it
[12:26]  * didrocks would want some sun now :(
[12:26]  * davmor2 doesn't believe Laney has it, you sure it is not a Police search helicopter light?
[12:40] <desrt> Good morning all
[12:41] <desrt> time to get my coffee, croissant, and a side of HIDEOUS ABI BREAKAGE
[12:41] <desrt> yum
[12:42] <Laney> hi desrt! :D
[12:43] <desrt> will take a look :)
[12:43] <Laney> maybe just a missing available annotation?
[12:43]  * Laney wants a croissant
[12:43] <desrt> ya.  visibility is the first thought that occurred to me too
[12:44] <desrt> since I'm fairly sure the definitions are being properly emitted
[12:44] <desrt> but seriously... the abi thing was third in that list for a good reason :)
[12:45] <didrocks> good morning desrt!
[12:45] <desrt> moin :)
[12:45] <xnox> =(
[12:45] <xnox> desrt, what abi breakage?!
[12:46] <didrocks> xnox: a gliby thingy
[12:46] <didrocks> xnox: http://irclogs.ubuntu.com/2015/11/25/%23ubuntu-desktop.html#t10:46
[12:47] <desrt> inlining in glib has been a disaster for a while -- we had inline versions in headers and backup versions in the .c file in case the compiler that you were using to build your project which included the headers didn't suport inlining
[12:47] <desrt> we gave up on that now since all compilers do inlining
[12:47] <desrt> so i cleaned up a lot of that mess, and tried to preserve the old versions for strict ABI compatibility
[12:47] <desrt> but clearly failed :)
[13:44]  * desrt escapes key-fob insanity
[13:44]  * desrt dives into ABI insanity
[13:46] <desrt> our building has massive keyfobs that double as garage-door-openers and i'm tired of carrying mine around... and i've long suspected that the transmitter and keyfob aspects of it operate separately... so i took it apart today to figure out which part of it was responsible for each
[13:47] <desrt> oddly enough, the thing stopped working after i took it out of the case
[13:47] <desrt> turns out the nfc/rfid bit is the back panel of the case itself
[13:49] <desrt> Laney: visibility was indeed the problem.  want a new release today?
[13:49] <desrt> (i already pushed the fix if you want to cherrypick it in the meantime)
[14:05] <Laney> desrt: probably a good idea, other distros might pick it up and not notice
[14:05] <willcooke> larsu, I'm going insane here.  My padding is being ignored for buttons in gedit, but everything else (like a test background colour) is being applied
[14:05] <willcooke> ?!
[14:05] <Laney> thanks for fixing
[14:05] <willcooke> any ideas?
[14:07] <willcooke> when I paste it in to the inspector it works
[14:07] <seb128> willcooke, what rule do you use?
[14:07] <willcooke> don;t understand "rule"
[14:08] <willcooke> css selector?
[14:09] <seb128> sorry, what lines do you add to the css
[14:09] <seb128> so we can try
[14:10] <willcooke> I'll pastebin it
[14:10] <larsu> willcooke: you can see in the inspector where a value comes from
[14:10] <larsu> in "style properties"
[14:10] <larsu> it tells you file and line nr
[14:10] <willcooke> larsu, it's blank
[14:11] <larsu> then your rule doesn't apply
[14:11] <willcooke> but the b/g colors *are* being applied
[14:11] <larsu> what is it? Do you have a branch?
[14:11] <willcooke> pastebin.ubuntu.com/13502453
[14:11] <willcooke> http://pastebin.ubuntu.com/13502453
[14:12] <larsu> hehe I was about to complain about the non-clickiness of that first link ;)
[14:12] <willcooke> :)
[14:12] <larsu> that's apps/gedit.css?
[14:13] <willcooke> yeah
[14:22]  * willcooke wonders if it could be some of the @xyz definitions being wrong for our theme
[14:23] <larsu> willcooke: ya, that seems to be it indeed (remove the "theme_" prefix)
[14:27] <willcooke> heh, thanks larsu, sorry to bother you with that
[14:28] <larsu> no worries :)
[14:28] <Laney> pitti: do you know if we're allowed to use backports in cloud deployed things?
[14:28] <Laney> trusty doesn't have a new enough lmdb, but I could backport it
[14:28] <pitti> Laney: I'm not sure that we even have a policy about what you can use
[14:29] <Laney> that sounds great to me ;-)
[14:29] <pitti> Laney: indeed trusty is pretty strongly recommended, but as long as you keep stuff updated backports sohuld be fine
[14:29] <Laney> I thought it was pretty tight
[14:29] <Laney> but actually I found a page about dev managed stuff even in prodstack
[14:29] <Laney> so if you get full control...
[14:29]  * Laney goes hog wild
[14:29] <pitti> Laney: I need a newer twitter-bootstrap3 for debci as well
[14:30] <Laney> pitti: I saw something where you wget a deb from the archive
[14:30] <Laney> that was great :P
[14:30] <pitti> Laney: yes, I manage autopkgtest myself, it's not CI managed
[14:30] <pitti> Laney: well, it's an utter hack, but *shrug*
[14:30] <Laney> pitti: this is prodstack, right?
[14:30] <pitti> yes
[14:30] <Laney> just the workers in scaling?
[14:30] <Laney> cool
[14:31] <pitti> Laney: the adt testbeds are in scaling; the workers themselves are on a PS instance
[14:31] <Laney> yeah sorry, that's what I meant
[14:31] <pitti> Laney: what are you charming up, OOI?
[14:31] <Laney> appstream extractor
[14:32] <Laney> another thing I'm not sure about is how to handle the cinder volume holding the archive mirror
[14:32] <Laney> it'd be a pain to have to start this from fresh each time
[14:32] <Laney> so maybe I can do it out of band
[14:32] <pitti> Laney: archive mirror?
[14:32] <Laney> juju doesn't seem to support this in the way I want yet
[14:32] <Laney> yeah, need a local one
[14:33] <pitti> Laney: ah, you want to attach a separate storage to your instance with that data
[14:33] <Laney> yes, it shouldn't be tied to the unit(?)
[14:33] <Laney> otherwise you have to re-mirror from scratch each time
[14:33] <pitti> Laney: where "each time" is just "when you redeploy", no?
[14:33] <pitti> which should happen like twice a year
[14:33] <pitti> so I wouldn't sweat that too much
[14:34] <pitti> Laney: and the mirror that you get in the cloud is pretty fast already
[14:34] <Laney> don't know
[14:34] <Laney> it's still a multiple hour operation
[14:34] <pitti> Laney: TBH I'd just start with setting up debmirror as part of your charm
[14:34] <pitti> Laney: you can upgrade a charm, you don't always need to re-deploy from scratch
[14:35] <Laney> I thought I might have the deploy script handle attaching a volume
[14:35] <pitti> welll, that indeed sounds elegant
[14:35] <Laney> i.e. do it out of band
[14:36] <pitti> Laney: I found that you can't charm quite a number of things anyway; you're going to need some deploy.sh script which invokes the various juju deploy, juju add-relation etc. commands, so you can do it there too
[14:36]  * Laney shrugs, will see, maybe it does prove to not be required that often
[14:36] <Laney> it would also be good to store the assets themselves in a resillient fashion
[14:36] <Laney> so after a redeploy we can serve the latest run until we catch up again
[14:37] <Laney> maybe I'm overthinking this for this early stage :)
[14:37] <pitti> Laney: so you can deploy your service
[14:37] <pitti> Laney: then use direct OpenStack commands to add the storage to your newly created machine
[14:38] <Laney> yeah, that bit should be fine
[14:38] <Laney> and I store the assets on this volume too
[14:39] <pitti> machine_no="$($(juju status myservice) | grep machine: | grep -o '[0-9]\+')"
[14:39] <pitti>     machine=juju-${env}-machine-${machine_no}
[14:39] <pitti> and then $machine is the thing to talk to with openstack commands line nova
[14:54] <Trevinho> desrt: hey, do you know what's the best way to get a gfile uri to be transformed to the actual path? I.e. I'd like to get the actual path from "trash://"
[14:59] <larsu> Trevinho: g_file_get_path()
[14:59] <larsu> it returns NULL though for things that don't have a path
[15:00] <Trevinho> larsu: tried in python but I get nothing
[15:00] <larsu> including trash://, I think
[15:00] <Trevinho> that's the thing
[15:00] <Trevinho> if you don't initialize it with a path, it won't work
[15:00] <larsu> trash isn't really a path...
[15:00]  * Trevinho wonders what nautilus uses
[15:00] <larsu> gio api
[15:01] <Trevinho> yeah, I know.. I mean, what it uses to get the proper path to show
[15:01] <larsu> where does it show that?
[15:01] <Trevinho> I mean, when you open trash:// in the location bar, it just open it as an ur and then fetches the children of that, or it maps to the real path to show?
[15:09] <larsu> Trevinho: it fetches the children with gio api
[15:09] <larsu> there's no path on the file system mapping to that
[15:10] <Trevinho> Mh, I see..
[15:10] <desrt> Trevinho: what larsu said
[15:10] <desrt> Trevinho: imagine you have http:// uri
[15:10] <Trevinho> Well the thing is that if you go in the trash, the you open a subfolder...
[15:10] <desrt> some GFile's simply do not have a path
[15:10] <Trevinho> nautilus open the actual paths
[15:10] <Trevinho> path*
[15:10] <Trevinho> the location is not trash://subfolder
[15:11] <desrt> that seems odd
[15:11] <Trevinho> err trash:///subfolder
[15:11] <desrt> curiously, i also see the same
[15:11] <desrt> nautilus may have some special code to do this
[15:11] <Trevinho> yeah, that's why I was wondering how to dothat...
[15:11] <desrt> pretty sure there is nothing on GIO API to support this
[15:12] <desrt>   standard::target-uri: file:///home/desrt/.var/lib/Trash/files/trashthis
[15:12] <desrt> so there you go
[15:12] <larsu> errr where do you see this?
[15:12] <Trevinho> standard::target-uri ?
[15:12] <desrt> gvfs-info
[15:13] <desrt> this is very strange, since the type of the thing is a directory
[15:13] <desrt> i wonder why i did that.....
[15:14] <larsu> no sorry, I mean in nautilus
[15:14] <desrt> i didn't do it.  it was hadess
[15:14] <larsu> I don't see the target-uri btw
[15:14] <desrt> see https://bugzilla.gnome.org/show_bug.cgi?id=667794
[15:16] <desrt> so there you go
[15:16] <desrt> Trevinho: my official answer is "it didn't used to do that but now it does and i don't really understand the reason"
[15:17] <Trevinho> mh, ok :-D
[15:17] <desrt> "so that totem can play DVDs from the trash"
[15:17] <desrt> (!)
[15:17] <larsu> wtf? Seriously?
[15:17] <desrt> that's what the commit says :)
[15:20] <larsu> sigh
[15:20] <desrt> anyway
[15:20] <desrt> Laney: new glib release is out
[15:21] <Laney> yay
[15:21] <desrt> hopefully this one isn't hideously broken
[15:21] <Trevinho> desrt: so.... There's no really way to get me the actual trash path?
[15:21] <desrt> Trevinho: but there is!
[15:21] <desrt> examine the standard::target-uri property, i guess
[15:21] <Trevinho> desrt: a part from going trhough children..
[15:21] <desrt> you can query it from g_file_query_info
[15:21] <Trevinho> desrt: there's nothing for gvfs-info trash:///
[15:22] <desrt> it has to be on a file in the trash
[15:22] <Trevinho> desrt: there's for gvfs-info trash:///trashed-child
[15:22] <desrt> trash:/// isn't an actual location
[15:22] <desrt> it is a combination of several locations (for example trash folders on removable media)
[15:22] <Trevinho> yeah, but I wanted to get from trash:/// -> file:///home/marco/.local/share/Trash/files/
[15:22] <desrt> different items can be in different actual locations
[15:22] <Trevinho> mh
[15:22] <desrt> if you want to know the homedir one, the answer is simple
[15:23] <desrt> by the spec it's in XDG_DATA_HOME/Trash/files
[15:23] <Trevinho> desrt: ok, that's what I wanted to use...
[15:23] <desrt> g_get_user_data_dir()
[15:23] <Trevinho> desrt: but you defined data_home on ~/.var/lib ?
[15:23] <larsu> Trevinho: what are you doing?
[15:23] <desrt> Trevinho: i set my XDG_DATA_HOME to that
[15:24] <Trevinho> larsu: launcher icons <-> storage windows matching
[15:24] <Trevinho> desrt: ok, then I'd go for that then
[15:24] <desrt> read http://standards.freedesktop.org/trash-spec/trashspec-1.0.html
[15:24] <desrt> but consider removable media
[15:24] <larsu> Trevinho: shouldn't that matching be on the uri, and not on the path?
[15:25] <Trevinho> desrt: yeah, that's the thig
[15:25] <Trevinho> larsu: in fact I was doing it using the URI...
[15:25] <desrt> just use GFile...
[15:25] <desrt> you do not want to reimplement the trash spec
[15:25] <larsu> nautilus windows tell you on dbus what they are showing right now (as a URI)
[15:25] <desrt> says someone who has implemented the trash spec
[15:25] <Trevinho> larsu: then...
[15:26] <desrt> when the logic should be:
[15:26] <desrt> "did the user click on something that IS A SYMLINK AND has a symlink destination?  go to it."
[15:27] <desrt> why hadess sets symlink destination on a directory?  no idea.
[15:28] <Trevinho> desrt: so you'd say we should fix nautilus or..... just use a workaround in unity side?
[15:30] <larsu> fix nautilus :)
[15:30]  * larsu hides
[15:30] <desrt> Trevinho: i'm chatting with hadess.  i think we need to fix gvfs.
[15:30] <desrt> we should also think about fixing nautilus while we're at it
[15:32] <Trevinho> desrt: ok, thanks... Let me know what's the final decision...
[15:32]  * Trevinho drives back to Florence
[15:32] <seb128> Trevinho, safe drive!
[15:32] <Trevinho> snow allert :o
[15:33] <Trevinho> seb128: thanks
[15:41] <seb128> tedg, hey, do you remember what is the deal with bug #1165420? did we remove indicators content from the hud on purpose? or was it a side effect of the gmenu transition?
[15:45] <attente> hi, does anyone know or have a debian/watch file for github releases?
[15:52] <seb128> attente, ibus has one
[15:52] <seb128> https://github.com/ibus/ibus/releases .*/ibus(?:-|_|_v|V)(\d\S*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz)
[15:52] <seb128> unsure if it works though
[15:54] <attente> seb128: thanks, i will try it
[16:09] <xnox> checking for XMIRMODULES... no
[16:09] <xnox> checking whether to build Xmir DDX... yes
[16:09] <xnox> configure: error: Xmir build explicitly requested, but required modules not found.
[16:09]  * xnox needs help
[16:09] <seb128> xnox, where is that?
[16:10] <xnox> seb128, on s390x
[16:10] <seb128> robert_ancell would probably be your best bet but he's sleeping at this time
[16:10] <xnox> i guess i should skip it, just like it is skipped on arm64, powerpc and ppc64el
[16:10] <seb128> maybe bregma or ChrisTownsend or tedg can help you
[16:10] <seb128> yeah, probably
[16:10] <xnox> #shame -> i already bootstrapped mir
[16:59] <tedg> seb128, it was removed because it failed in user testing. The plan was to bring it back with additional info, but it never got implemented.
[17:00] <seb128> tedg, ok, seems quite some users liked/would like that (me included), I was wondering if that was something to "fix" for the LTS
[17:00] <seb128> I though it was buggy
[17:00] <seb128> not disabled on purpose
[17:00] <tedg> Sadly, no clue on Mir. Try #ubuntu-Mir
[17:01] <seb128> I would argue that the audiance that uses hud is probably not confused by indicators being listed in there
[17:01] <tedg> seb128, I am +1, I doubt there is anyone in design that remembers that user study anyway ;-)
[17:02] <seb128> would it be easy to re-enable? do you remember where that was changed?
[17:02] <tedg> seb128, it has been rewritten since...
[17:02] <seb128> oh, right :-/
[17:02] <seb128> tedg, thanks
[17:03] <seb128> so a valid wishlist but not likely trivial
[17:03] <tedg> But we now have an indicator registry, so it should be easier now.
[17:07] <seb128> tedg, k, let's see if somebody can pick it up as LTS polish, I put it on the list
[17:38] <didrocks> good night everyone!
[17:39] <willcooke> cya didrocks
[17:39] <didrocks> see you!
[17:55] <Trevinho> desrt: got anything from that discussion?
[17:55] <desrt> annoyingly, no
[17:55] <Trevinho> desrt: mh, so... going for a workaround for now
[18:03] <desrt> Trevinho: we're still chatting about it
[18:03] <desrt> Trevinho: but sure... more workarounds are cool too
[18:04] <Trevinho> desrt: well, I don't love them, but if we can't find a better solution upstream...
[18:04] <desrt> we can
[18:04] <desrt> but you haven't given much time
[18:04] <Trevinho> maybe :-)
[18:05] <Trevinho> I was wondering... In case of a subfolder trashed on an external device...
[18:05] <Trevinho> what's its uri?
[18:05] <Trevinho> I mean, trash://media-id/folder or what?
[18:10] <attente> seb128: could i submit a new package for upload to the archive?
[18:22] <Laney> glib uploaded to sync tomorrow, some first work on appstream charm pushed
[18:22] <Laney> LATERS
[19:13] <Sweet5hark> willcooke: fyi http://nabble.documentfoundation.org/Candidacy-Bjoern-Michaelsen-td4167393.html
[19:14] <willcooke> Sweet5hark, good stuff!  Good luck
[19:15]  * Sweet5hark starts kissing babies and buys a smear campaign on TV.
[19:55] <ricotz> Sweet5hark, lol, thumbs up
[20:48] <willcooke> alrighty!!!
[20:48] <willcooke> I have vanquished by Gtk theme foes with a combination of brute force and ignorance
[20:48] <willcooke> I'll finish it tomorrow
[20:48] <willcooke> g'night all


[14:10] <Wiz_KeeD> hey guys, if I pull off a branch and then check a bit later if the repo which I've got the branch from has changed or not, basically comparing revision numbers, how would I go about that?
[14:11] <Wiz_KeeD> bzr revno parent?
[14:16] <Plouj> how can I view specific files in this repo in my browser: http://anonscm.debian.org/bzr/pkg-ssh/openssh/squeeze/ ?
[14:17] <Plouj> Or this repo: http://bzr.debian.org/pkg-ssh/openssh/trunk
[21:03] <mark06> http://i.imgur.com/UHntlRD.png
[21:34] <mark06> http://bazaar.launchpad.net/~renatosilva/+junk/scripts/revision/148
[21:35] <mark06> http://bazaar.launchpad.net/~renatosilva/+junk/scripts/revision/149
[21:35] <lifeless> cool
[21:36] <mark06> thanks!


[12:04] <gnomefreak> i cant find the power button to my scanner :(
[12:14] <bdrung_> maybe it has none?
[12:22] <gnomefreak> bdrung_: it doesnt from what i can tell but xsane isnt seeing the scanner
[12:22] <gnomefreak> im thinking power cord is bad
[12:23] <bdrung_> if the scanner has power something should glow
[12:24] <gnomefreak> bdrung_: nothing is glowing thats what makes me think its power. i changed the usb port just incase it was bad but still no luck
[12:25] <gnomefreak> i have another one and ill get it later i guess or see if i have another power cord for it
[12:25] <bdrung_> hm
[15:26] <andv> bdrung_, who gonna advocate you for DM?
[15:26] <bdrung_> andv: don't know. i will ask all my sponsors.
[15:27] <andv> k
[15:37] <gnomefreak> bug 383670
[15:50] <micahg> gnomefreak: do you know anything about the issue regarding bug 417582
[15:51] <gnomefreak> micahg: lack of QT support maybe looking now
[15:51] <gnomefreak> hats not helpful in the least
[15:51] <micahg> I didn't know we even had that type of default configurable from Firefox on linux
[15:52] <gnomefreak> we dont IIRC however why should firefox detect something outside our repos?
[15:52] <gnomefreak> !info arora
[15:52] <micahg> yeah
[15:52] <gnomefreak> oh it is
[15:52] <micahg> it's the new KDE browser
[15:52] <gnomefreak> firefox has no reason to detect that browser
[15:53] <micahg> that's what I figured
[15:53] <micahg> that it's handled differently than windows
[15:53] <gnomefreak> the default browser changes should be made in update-alternatives
[15:53] <micahg> do we support that at present?
[15:53] <gnomefreak> update-*?
[15:54] <micahg> yeah
[15:54] <gnomefreak> Ubuntu does we dont
[15:54] <micahg> ah
[15:54] <gnomefreak> well kind of
[15:54] <gnomefreak> we have links in our packages for the update-alternatives so you can shoose it from that setting
[15:54] <micahg> oh, ok
[15:54] <gnomefreak> s/shoose/choose
[15:55] <gnomefreak> KDE should have a default browser setting in menu
[15:55] <gnomefreak> if not that is thier issue
[15:55] <micahg> they probably do
[15:59] <bdrung_> andv: now i see why you asked. :)
[16:00] <andv> bdrung_, why?
[16:00] <andv> :)
[16:00] <bdrung_> andv: you apply for it, too
[16:00] <andv> bdrung_, yeah
[16:00] <andv> bdrung_, soon a new package revision will be uploaded
[16:01] <bdrung_> of what?
[16:01] <andv> bdrung_, so you should find an advocate / attach a changset asap
[16:01] <andv> bdrung_, of debian-maintainers package
[16:01] <bdrung_> andv: i have send an email to 8 DDs, so hopefully someone will advocate me.
[16:02] <gnomefreak> micahg: there maybe a setting in arora to make it default like there is in firefox
[16:03] <andv> bdrung_, yeah^^
[16:03] <andv> bdrung_, prepare your changeset then
[16:08] <bdrung_> andv: do i need an advocate to create the changeset?
[16:08] <andv> bdrung_, yes
[16:08] <andv> bdrung_, in the changeset you have to list all your advocations
[16:09] <bdrung_> ah, ok
[21:24] <BUGabundo> ola
[21:29] <fta> gni
[21:31] <BUGabundo> hi fta
[21:35] <fta> it's quiet in here
[21:35]  * micahg has questions, but they are for the man on vacation :)
[21:36] <BUGabundo> ehehe
[21:37] <BUGabundo> so are you saying asac is the one that brings noise here?
[21:37] <micahg> no
[21:37] <BUGabundo> ok
[21:37] <BUGabundo> :D
[21:37] <micahg> just explaining why I'm not making nay
[21:37] <micahg> *any
[22:53] <[reed]> armin76: ping
[22:54] <[reed]> where's asac, hmmz
[22:54] <[reed]> jdstrand: around?
[22:54] <andv> [reed], asas is on vacation
[22:54] <andv> :)
[22:54] <[reed]> ah
[22:54] <jdstrand> [reed]: yes
[22:54] <jdstrand> [reed]: what's up?
[22:57] <[reed]> jdstrand: msg'd you
[23:06] <jdstrand> ack
[23:11] <e-jat> fta : here?
[23:11] <fta> e-jat, 1/2
[23:11] <e-jat> half ? :)
[23:12] <fta> yes
[23:12] <e-jat> fta is your chromium still having the flash issue ?
[23:13] <e-jat> is it must me 1 plugin show at about:plugins?
[23:13] <e-jat> i mean for the flash ..
[23:13] <fta> e-jat, when i tried, it was crashing, i filed http://code.google.com/p/chromium/issues/detail?id=20045
[23:13] <fta> not sure your bug is the same
[23:15] <e-jat> for me is not crash .. but it cant view/render video from the youtube ..
[23:15] <[reed]> you should just use Firefox ;)
[23:15] <e-jat> [reed]: yea :)
[23:15] <fta> [reed], ff trunk is unusable for me, it just refuses to start
[23:15] <[reed]> fta: ?
[23:15] <[reed]> fta: works fine for me
[23:15] <fta> x64
[23:16] <fta> 32bit is fine
[23:16] <[reed]> hmm, you should tell me these things!
[23:16] <[reed]> do you have ia32-libs installed?
[23:16] <fta> you disappeared for weeks
[23:16] <[reed]> you can always e-mail me ;)
[23:17] <fta> i use x64 at work, and i have better things to do than debug my browser
[23:17] <[reed]> well, we want Firefox to work everywhere
[23:18] <[reed]> so, if you can spare some time to debug it, that would be awesome
[23:18] <[reed]> and hopefully we can get it fixed
[23:18] <fta> 3.6 is still fine
[23:18] <[reed]> I use official mozilla.org nightlies for trunk (3.7) on jaunty
[23:19] <[reed]> but I'm also i686
[23:21] <fta> well, what could i say? it's been broken for at least a week for me on karmic x64
[23:21] <[reed]> yeah, well, can you give any more information?
[23:21] <fta> no crash, no error, no nothing, just no window and i'm back to the shell (when started from a shell)
[23:22] <[reed]> does gdb say anything?
[23:22] <fta> strace shows that it starts well, then it releases the lock and exit
[23:22] <[reed]> hmm
[23:22] <BUGabundo> I'm on 3.7
[23:22] <BUGabundo> dailly ppa
[23:22] <BUGabundo> works ok
[23:22] <BUGabundo> on 64bits
[23:22] <fta> nope, gdb does help, it doesn't catch anything
[23:22] <BUGabundo> only prob: Fullscreen bug
[23:22] <[reed]> BUGabundo: x86_64?
[23:23] <[reed]> BUGabundo: fullscreen bug?
[23:23] <BUGabundo> [reed]: ^^^^
[23:23] <BUGabundo> https://bugzilla.mozilla.org/show_bug.cgi?id=511080
[23:23] <[reed]> fta: hmm, could you try building debug?
[23:23] <fta> for me, it works only once after each upgrade, the next day in the morning, nada
[23:24] <[reed]> hmm
[23:24] <BUGabundo> fta start in safemode, quit, start again it work
[23:25] <BUGabundo> been like that for 4 months  :(
[23:25] <BUGabundo> better now in 3.7
[23:25] <BUGabundo> but still fails to start sometimes
[23:25] <[reed]> BUGabundo: so, it works 20090816 but not 20090817 ?
[23:25] <[reed]> heh
[23:25] <BUGabundo> greasemokey does make it worse
[23:25] <[reed]> have you filed a bug on that?
[23:25] <BUGabundo> [reed]: at least one mine on LP
[23:26] <BUGabundo> [reed]: let me test it again with todays build
[23:26] <BUGabundo> I haven't done it yet
[23:26] <[reed]> k
[23:26] <BUGabundo> I didn't even got updates :\\
[23:26] <[reed]> need to find a regression range to really figure it out
[23:26]  * BUGabundo runs $ sudo aptitude update ; sudo aptitude safe-upgrade ; sudo aptitude full-upgrade
[23:27] <BUGabundo> [reed]: that's why I posted the Revision
[23:27] <BUGabundo> and that's what Dailies are for :)
[23:27] <[reed]> yeah, so, it works 20090816 but not 20090817 ?
[23:29] <BUGabundo> right
[23:30] <[reed]> hmm
[23:34] <[reed]> maybe mozilla bug 503791
[23:36] <BUGabundo> hum??
[23:36] <BUGabundo> that's not my bug
[23:36] <BUGabundo> not even close
[23:36] <BUGabundo> don't start spewing bug, or else  ill start thinking I have them all :D
[23:37] <[reed]> I'm looking at patches that landed
[23:37] <[reed]> http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2009-08-16+&enddate=2009-08-18
[23:37] <BUGabundo> ahh
[23:37] <BUGabundo> [reed]: what would it take to debug what the F**k is causing gmail to kill my firefox?
[23:37] <BUGabundo> it eats all my cpu
[23:37] <BUGabundo> prob one of my addons
[23:38] <BUGabundo> but I disabled them all and still got it
[23:38] <BUGabundo> it happenes on both ubuntu and debian
[23:38] <fta> [reed], i also have huge repaint problems with trunk, mostly forums
[23:38] <BUGabundo> with the daily ppa
[23:38] <BUGabundo> on 3.6 and 3.7
[23:38] <BUGabundo> humm I have that too
[23:38] <BUGabundo> though it was a debian X bug
[23:39] <[reed]> fta: just trunk?
[23:39] <[reed]> 3.6 is fine?
[23:40] <fta> [reed], i assume the new ff is a security update, right? (3.0.14 & 3.5.3)
[23:40] <[reed]> yes
[23:41] <[reed]> nothing special
[23:41] <fta> too bad it's in main, i'm only a motu and i can't update it there
[23:41] <[reed]> just normal update
[23:41] <[reed]> scheduled release is September 9th
[23:42] <fta> maybe with the archive reorg, i will gain that power...
[23:42] <fta> or loose everything :P
[23:42] <BUGabundo> eeh
[23:42] <BUGabundo> you should
[23:43] <micahg> 3.5.3 has some other fixes unless they were pushed back
[23:43] <[reed]> security & stability update
[23:43] <[reed]> :)
[23:43] <micahg> :)
[23:43] <micahg> I started tagging the fixed versions in LP since we don't have a system to handle that yet
[23:45] <[reed]> https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20status1.9.1:.3-fixed
[23:45] <[reed]> I see 53 bugs fixed
[23:45] <micahg> I see 42 :)
[23:45] <fta> 42+11 private?
[23:45] <fta> :)
[23:46] <micahg> at least 3 we have in LP
[23:46] <micahg> including the full screen flash issue
[23:47] <bdrung_> micahg: 42 :)
[23:48] <bdrung_> that's the right number
[23:48] <micahg> bdrung_: [reed]sees 53
[23:49] <fta> yep, 42 :)
[23:49] <fta> i mean, "the" number
[23:49] <[reed]> micahg: reed is also a member of the security group ;)
[23:49] <micahg> right :)
[23:49] <bdrung_> fta: :)
[23:50] <bdrung_> fta: you got it
[23:50] <fta> sure, 42, the Answer to Life, the Universe, and Everything
[23:52] <micahg> [reed]: is there a document on how  crashes are labeled  in  bmo
[23:52] <[reed]> micahg: https://developer.mozilla.org/En/Triaging_crash_bugs
[23:53] <micahg> ty
[23:53] <micahg> that will help to see if it's an upstream issue
[23:53] <BUGabundo> fta "but what is the question?" ehehe
[23:54]  * micahg knows...
[23:55] <micahg> [reed]: is this anything? http://seclists.org/bugtraq/2009/Aug/0194.html
[23:55] <[reed]> looks like just a DoS... I don't know of a bug in bmo that's tracking it, though
[23:56] <micahg> do I need to worry about opening a bug for it?
[23:56] <micahg> or is it not an issue
[23:56] <[reed]> well, it's an "issue", but I don't know if we're tracking it yet
[23:56] <micahg> ah, ok
[23:56] <[reed]> feel free to open a new bmo bug
[23:57] <micahg> ok
[23:57] <micahg> mabe later tonight
[23:57] <[reed]> it's public, but I still would recommend you check the "this bug is a security issue" box so that the security group triages it rather than the normal triagers
[23:57] <micahg> ok
[23:57] <[reed]> even though it's public
[23:57] <[reed]> it just works out better that way
[23:57] <micahg> I figured I'd open one in Launchpad as well
[23:58] <[reed]> sure
[23:58] <[reed]> won't be long before launchpad and bmo can be linked
[23:58] <[reed]> just waiting on bmo to upgrade
[23:58] <micahg> really?
[23:58] <[reed]> yeah
[23:58] <micahg> that's great
[23:58] <micahg> how would that work?
[23:58] <micahg> I could just say push upstream?
[23:58] <[reed]> afaik, Bugzilla 3.4 supports everything launchpad needs in order to link
[23:58] <[reed]> no
[23:59] <[reed]> means you can link bugs
[23:59] <[reed]> and comments will flow from one to the other
[23:59] <micahg> ah, well
[23:59] <micahg> that's good and bad
[23:59] <micahg> reporters might not always be interested in upstream comments, but I think triagers would be


[07:53] <Wizard> Good morning.
[08:06] <Wizard> Could somebody help me with bug report? :(
[08:06] <Wizard> https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1051331
[08:06] <ubot2> Launchpad bug 1051331 in unity-lens-applications "Aplication lens "All" button doesn't expand" [Undecided,New]
[08:07] <Wizard> I've noticed it affects other lenses too, but I don't know how to "add" packages.
[08:16] <hjd> Wizard: Hi. This isn't exactly obvious, but if you click "Also affects distribution" and select Ubuntu, you can add additional packages.
[08:17] <Wizard> Is it how I should do this?
[08:22] <hjd> Yes, if the other lenses are Ubuntu packages.
[08:27] <Wizard> They are, hjd.
[08:27] <Wizard> Btw, this bug is annoying ;P
[08:51] <Wizard> hjd: Done, could you, please, look again?
[09:17] <hjd> Wizard: Looks ok. :)
[09:18] <hjd> Though after thinking about it, I wonder whether these buttons are part of the lens, or defined by unity itself. I don't know how this is organized though...
[09:19] <Wizard> Me neither.. I hope people responsible for this will know :)
[09:20] <hjd> Well, now that it spans multiple packages, hopefully someone will notice it. Looks really annoying so thanks for reporting. :)
[09:22] <Wizard> You're welcome.
[09:23] <Wizard> I think, more importantly, it spans multiple languages.
[19:01] <penguin42> could someone check my logic on bug 218837 ?
[19:01] <ubot2> Launchpad bug 218837 in ksh "Assigning instead of Comparing " [Undecided,Invalid] https://launchpad.net/bugs/218837
[19:01] <penguin42> I've just marked it invalid
[19:02] <penguin42> oops, just added another line to my explanation
[19:03] <penguin42> I can see why the reporter was confused though, that is the most disgusting code I've seen in years
[19:08] <TheLordOfTime> i've seen some pretty damn ugly code, that tops it all though
[19:08] <penguin42> TheLordOfTime: That's original ksh source
[19:08] <TheLordOfTime> this's an old bug o.O
[19:08] <penguin42> TheLordOfTime: I like triaging old bugs, there are some real gems
[19:08] <TheLordOfTime> :P
[19:08] <TheLordOfTime> i'm not checking logic today though
[19:08] <TheLordOfTime> too busy studying for my stats exam on tuesday
[19:08] <penguin42> TheLordOfTime: Good luck!
[19:09] <penguin42> TheLordOfTime: What are the chances of you passing?
[19:09] <TheLordOfTime> 95%
[19:09] <TheLordOfTime> even without studying
[19:09] <TheLordOfTime> 85% I get a 95% or higher
[19:09] <TheLordOfTime> 80% I get an A
[19:09] <TheLordOfTime> 75% chance I get a B
[19:09] <TheLordOfTime> and yes, those numbers do NOT add up to 100%
[19:10] <penguin42> :-)
[19:12] <penguin42> time to disappear - good luck!
[19:19] <njin> Hallo bug 1045517 is private, can be unlocked ?
[19:19] <njin> Thanks
[19:22]  * TheLordOfTime looks
[19:23] <TheLordOfTime> ... SERIOUSLY?
[19:23] <TheLordOfTime> LP keeps timing out
[19:23]  * TheLordOfTime blames  Comcast
[19:25] <njin> yes, apport show me that page but is locked
[19:26] <njin> probably private
[20:59] <jeroen> Hello, can someone help me with this bg I have? My Quadro 2000M is acting glitchy after installing the nvidia-current 304.43 driver on Ubuntu 12.10
[21:00] <jeroen> That version should support my card. 295 on Ubuntu 12.04 has worked perfectly before


[01:03] -lugito:#lubuntu-devel- [rLUGITO838fc1d0ec8d: Make Jenkins a connector.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO838fc1d0ec8d
[01:04] -lugito:#lubuntu-devel- [rLUGITO5f24aa73758c: Add Jenkins support.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO5f24aa73758c
[01:05] -lugito:#lubuntu-devel- [rLUGITOaf8caba6f5f3: Make sure package_names is also recognized as a subdict.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITOaf8caba6f5f3
[01:05] -lugito:#lubuntu-devel- [rLUGITOe6afdab9e12b: Add jenkins to the init.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITOe6afdab9e12b
[01:11] -lugito:#lubuntu-devel- [rLUGITO96c73754dbc1: Ensure pkg_name is defined.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO96c73754dbc1
[01:51] -lugito:#lubuntu-devel- [rLUGITO266bf68d477f: Implement a get_repository_name function to use with the Jenkins function.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO266bf68d477f
[02:07] -lugito:#lubuntu-devel- [rLUGITO6b70f393f821: phab is a global variable, treat it as such.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO6b70f393f821
[02:11] -lugito:#lubuntu-devel- [rLUGITO913f68fcd8ec: Correctly pass the all-lowercase repo name.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLUGITO913f68fcd8ec
[02:21] -lugito:#lubuntu-devel- [rPPABRITNEY64dd1fc40596: Instead of removing britney_output on each run, just create a new timestamp.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rPPABRITNEY64dd1fc40596
[02:40] <guiverc> https://phab.lubuntu.me/w/release-team/testing-checklist/?v=17 is as far as I got... None of my own hardware has UEFI  (it's all too old) & I couldn't work out the setup for the secure boot option (it's disabled with no ability to change; if it's in key management I don't know it on the thankfully not my ultracrapbook)
[02:41] <tsimonq2> You're awesome guiverc!
[02:41] <tsimonq2> Thank you!
[02:41] <tsimonq2> I went ahead and published your draft.
[02:42] <kc2bez> That is awesome guiverc!
[02:42] -lugito:#lubuntu-devel- [rCIMETADATAf755dd253b5d: Add lxqt-archiver, nm-tray, trojita.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rCIMETADATAf755dd253b5d
[02:44] <tsimonq2> guiverc: You might want to consider enabling 2FA in Phab and setting a profile picture :)
[02:45] <tsimonq2> kc2bez: While I'm at it, perhaps you would consider setting a profile picture as well
[02:45] <tsimonq2> lynorian: ^
[02:45] <kc2bez> I can put my ugly mug up there XD
[02:45] <tsimonq2> ok XD
[02:46] <lynorian> I need to shave first probably
[02:46] <lynorian> if I use a new picture
[02:46] <tsimonq2> Makes it easier to identify people when editing/viewing tasks en masse
[02:46] <tsimonq2> lynorian: Up to you :)
[02:46] <tsimonq2> Your Telegram one would probably work fine.
[02:54] <lynorian> how big should I make it?
[02:54] <guiverc> changed pic - and it's not a dog  (a large aussie flightless bird).  (the only pic I know of me is somewhere on lp (ubuntu-news team somewhere))
[02:55] <tsimonq2> :D
[02:55] <tsimonq2> lynorian: However big it allows.
[02:55] <tsimonq2> Up to you (and Phab).
[02:55] <lynorian> well I had phab too big so I resized it smaller
[02:56] <tsimonq2> ok
[02:56] <lynorian> I resized it smaller
[02:58] -lugito:#lubuntu-devel- [rLXQTARCHIVERPACKAGING30100f2cae33: Remove reverse-applicable patch.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLXQTARCHIVERPACKAGING30100f2cae33
[03:00] -lugito:#lubuntu-devel- [rCI2b178685a051: Safely handle not being able to push; if we've made it this far, it should pass…] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rCI2b178685a051
[03:03] -lugito:#lubuntu-devel- [rTROJITAPACKAGING64ec73244b03: Remove reverse-applicable patches.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rTROJITAPACKAGING64ec73244b03
[03:05] -lugito:#lubuntu-devel- [rLXQTARCHIVERPACKAGING91894a70c4d4: Add a build dependency on libqt5x11extras5-dev.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLXQTARCHIVERPACKAGING91894a70c4d4
[03:10] -lugito:#lubuntu-devel- [rLXQTARCHIVERPACKAGING362cd882995a: Add a build dependency on libqt5x11extras5-dev, libfm-qt-dev.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLXQTARCHIVERPACKAGING362cd882995a
[03:15] -lugito:#lubuntu-devel- [rLXQTARCHIVERPACKAGINGce298723fd60: Remove files that are no longer installed.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLXQTARCHIVERPACKAGINGce298723fd60
[03:15] <tsimonq2> Thanks Dan and Lyn :)
[03:16] <kc2bez> :)
 @tsimonq2 [<tsimonq2> kc2bez: While I'm at it, perhaps you would consider setting a profile …], @aptghetto might be the last person I have to hunt down for this XD
[03:17] <tsimonq2> Oh, and teward, but he has a TODO list anyway. :P
[03:18] <tsimonq2> So, I just put lxqt-archiver, nm-tray, and trojita in the CI.
[03:18] <tsimonq2> nm-tray built fine, lxqt-archiver and trojita are FTBFS.
[03:19] <tsimonq2> kc2bez: Do you have the time tonight to walk through fixing this? :) https://ci.lubuntu.me/job/disco_trojita/
[03:20] -lugito:#lubuntu-devel- [rLXQTARCHIVERPACKAGINGfb0f7810e2d3: Move files from libexec to a standard usr/lib path.] tsimonq2 (Simon Quigley) committed: https://phab.lubuntu.me/rLXQTARCHIVERPACKAGINGfb0f7810e2d3
[03:21] <tsimonq2> Anyone else, too ^
[03:23] <kc2bez> Looking at it, can't guarantee anything XD
[03:23] <tsimonq2> Wanna give it a shot though? :)
[03:23] <tsimonq2> I can walk you through
[03:23] <kc2bez> Sounds good, I am willing.
[03:23] <tsimonq2> ok, cool
[03:24] <tsimonq2> First thing is to clone this via SSH: https://phab.lubuntu.me/source/trojita/
[03:24] <tsimonq2> When you have it cloned, check out the ci/unstable branch.
[03:38] <kc2bez> I am updating my VM be right back with you.
[03:38] <tsimonq2> ok :)
[03:53] <kc2bez> Ok I got it cloned and did a checkout ci/unstable
[03:54] <tsimonq2> Alright, so now let's look at the error.
[03:55] <tsimonq2> You can find the build logs here: https://launchpad.net/~lubuntu-ci/+archive/ubuntu/unstable-ci-proposed/+packages
[03:55] <tsimonq2> We're looking for the Disco build.
[03:55] <tsimonq2> amd64 is usually the one to look at because architecture-independent (or arch:all) builds are done on this architecture, as well as the amd64-specific build, if that makes sense.
[03:56] <tsimonq2> Here's the errors I'm seeing, the ones we should look at:
[03:56] <tsimonq2>    dh_install -O--buildsystem=cmake
[03:56] <tsimonq2> dh_install: Cannot find (any matches for) "usr/share/appdata/trojita.appdata.xml" (tried in ., debian/tmp)
[03:56] <tsimonq2> dh_install: trojita missing files: usr/share/appdata/trojita.appdata.xml
[03:56] <tsimonq2> dh_install: Cannot find (any matches for) "usr/lib/trojita/" (tried in ., debian/tmp)
[03:56] <tsimonq2> dh_install: trojita missing files: usr/lib/trojita/
[03:56] <tsimonq2> dh_install: Cannot find (any matches for) "usr/lib/libtrojita_plugins.so" (tried in ., debian/tmp)
[03:56] <tsimonq2> dh_install: trojita missing files: usr/lib/libtrojita_plugins.so
[03:56] <tsimonq2> dh_install: Cannot find (any matches for) "usr/share/trojita/locale" (tried in ., debian/tmp)
[03:56] <tsimonq2> dh_install: trojita-l10n missing files: usr/share/trojita/locale
[03:56] <tsimonq2> dh_install: missing files, aborting
[03:56] <tsimonq2> make: *** [debian/rules:10: binary] Error 25
[03:57] <lynorian> tsimonq2: don't get banned for excess flood
[03:57] <tsimonq2> lynorian: I've flooded worse. :P
[03:57] <tsimonq2> Anyway...
[03:57] <tsimonq2> kc2bez: With me so far?
[03:57] <kc2bez> Looking at the buildlog so yup
[03:57] <tsimonq2> ok cool
[03:58] <tsimonq2> So, when working with a single source package that produces multiple binary packages, the packager needs to lay out what files go where.
[03:58] <tsimonq2> If those files go missing in the future, the build fails.
[03:59] <tsimonq2> That's what happened here; we're using an upstream Git snapshot and the packaged version refers to a source from like a year ago.
[03:59] <tsimonq2> Unfortunately with this build log, it doesn't tell you which files have been removed and which files were simply moved since the last working state.
[04:00] <tsimonq2> So, you'll need to find the binary package it's referring to here, and remove each of the lines that have been referenced.
[04:01] <tsimonq2> The build log tells you basically everything you need to know here.
[04:01] <tsimonq2> For example, you're looking in debian/trojita.install for a line that has "usr/share/appdata/trojita.appdata.xml" and you just need to remove that.
[04:01] <tsimonq2> With me?
[04:02] <kc2bez> I'm still following.
[04:02] <tsimonq2> Cool.
[04:02] <tsimonq2> So, go through the lines that are referenced, remove them from the install files, and since you're working with the CI on the CI branch, git add, git commit, git push :)
[04:03] <tsimonq2> (If you were working with the archive, of course, you'd either use the CI, a PPA, or a local build to verify first. But, CI builds are fairly ephemeral, so I'm not really worried about it.)
[04:04] <kc2bez> Ok, sounds good.
[04:04] <tsimonq2> Cool; we'll get a notification here when you've pushed, and go from there :)
[04:29] -lugito:#lubuntu-devel- [rTROJITAPACKAGING297bae81a1d6: Remove references to missing files] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rTROJITAPACKAGING297bae81a1d6
[04:29] -lugito:#lubuntu-devel- [rTROJITAPACKAGING35dc10a00dff: Remove trojita-l10n.install file which references missing files] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rTROJITAPACKAGING35dc10a00dff
[04:30] <kc2bez> fingers crossed
 \o/
 Let's see what the CI thinks
 https://launchpadlibrarian.net/417100018/buildlog_ubuntu-disco-amd64.trojita_0.7+git201903302329~disco-0ubuntu1~ppa1_BUILDING.txt.gz
 Looks like you missed one :)
[04:37] <kc2bez> Gotter otter
[04:39] -lugito:#lubuntu-devel- [rTROJITAPACKAGING13abafe28153: Remove missing file reference] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rTROJITAPACKAGING13abafe28153
 Alright, the first pass is done!
 https://launchpadlibrarian.net/417100893/buildlog_ubuntu-disco-amd64.trojita_0.7+git201903302342~disco-0ubuntu1~ppa1_BUILDING.txt.gz
 All you have to do is put those back in the install file
 One thing to note though, "x86_64-linux-gnu" should always be replaced with "*" because that's arch-specific
[05:00] -lugito:#lubuntu-devel- [rTROJITAPACKAGINGeddd9435c90f: Add install file references] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rTROJITAPACKAGINGeddd9435c90f
[05:12] <tsimonq2> Niiiiiiiiice, this is a fun one.
[05:13] <tsimonq2> kc2bez: As far as the stuff you were doing is concerned, you're done; it worked. :)
[05:13] <kc2bez> \o/
[05:13] <tsimonq2> However...
[05:13] <tsimonq2> ppc64el and armhf (to start) seem to be FTBFSing because of some GPG-related thing.
[05:14] <tsimonq2> I have access to Debian machines running on those architectures; I'll debug tomorrow.
[05:14] <tsimonq2> If you have any ideas after seeing those build logs and want to try anything, you're more than welcome to.
[05:15] <tsimonq2> As with everyone else in the Development Team on Phab, I trust y'all to be able to use the CI as a playground and not horribly mess up stuff :)
[05:16] <kc2bez> Cool, thanks for the guidance. I have no intention of borking it trust me.
[05:16] <tsimonq2> hahah :)
[05:16] <tsimonq2> @acheronuk: trojita is being fun: https://launchpad.net/~lubuntu-ci/+archive/ubuntu/unstable-ci-proposed/+packages
[05:16] <tsimonq2> I hear that Rik guy recently became a MOTU ;)
[05:17] <kc2bez> I saw that too. Congrats to him :)
[05:17] <tsimonq2> He should have went for it a while ago ;)
[05:18] <tsimonq2> Anyway, I just kicked off a nightly in Jenkins; I'll go to bed I think.
[05:19] <kc2bez> I am heading to bed too. Thanks again, I appreciate it.
[05:19] <tsimonq2> No problem at all :)
[05:20] <tsimonq2> One other thing I just want to put out there; Lubuntu Members have access to trigger builds in Jenkins
[05:20] <tsimonq2> All you have to do is log in
[05:20] <tsimonq2> So if you ever see something awry, don't hesitate to button push :)
[05:20] <kc2bez> Ok thanks.
[05:20] <tsimonq2> Thank *you* :)
[05:27] <tsimonq2> Oh, I have an idea.
[05:28] <tsimonq2> guiverc: For the tests you marked as failed, could you try them again, except right before you do the install you enable ppa:lubuntu-ci/unstable-ci and log out/log back in (without rebooting)?
[05:28] <tsimonq2> I would totally be curious to see if anything magically fixes itself.
[05:38] <guiverc> tsimonq2, ack ... will do.
[05:38] <tsimonq2> Thanks!
[05:53] <guiverc> tsimonq2,  add-apt-repo without apt upgrade/dist-upgrade will do nothing - do you want me to upgrade or dist-upgrade?  i can re-test again if helpful..
[05:53] <tsimonq2> sudo apt -y full-upgrade
[05:53] <guiverc> :)
[05:54] <tsimonq2> Thanks again :)
[05:54] <guiverc> (no guarantee my fingers won't type dist-upgrade though....)
[05:55] <guiverc> 66 packages upgrading on first box...
[05:56] <tsimonq2> yup :)
[05:59] <guiverc> (my daily is out-of-date; new downloading; but proceeding with current re-test as full-upgrade should have caught everything I hope;  i can redo if required.. it'll may have installed pre-zsync download is done)
[06:14] <guiverc> tsimonq2, :(  Sorry, same result on BIOS full-disk encryption (1822237) - only change is UUID on no-such-device line...  zync has completed; will write it now, was their a kernel upgrade or somethign that could make it perform better if re-done with newer daily?
 Worth a shot :)
 @wxl[m] [<wxl[m]> @TheLoudSpeaker look what I found https://bugs.launchpad.net/ubuntu/+so …], I will have a look. Thanks!
[06:42] <guiverc> tsimonq2, possible untrained-monkey boo-boo.. i just noted re-doing it with 20190330 daily that boot-loader-location gets blanked on selecting encryption... maybe me noticing that is the cause of my FAIL reports... will explore
[06:43] <guiverc> ^ s/me noticing/me NOT noticing /
 still that would not be a good default
[06:46] <guiverc> the field (boot-loader-location) blanks only when you enter passphrase & you get the spinning-symbol as it validates it (I assume, it blanks during this stage)
[06:47] <guiverc> my install is running... I'll note it on lp.bug report 1822237 when done
 Thanks!
[06:51] <guiverc> you go to bed tsimonq2 (that time isn't it!)
 Hahaha
[06:56] <guiverc> :(  alas fail again, but will keep exploring this..
[08:49] <guiverc> :(  fail on "Full disk install with encryption on a EFI system without secure boot" using 20190330 daily (no ppa)
 @tsimonq2 [<tsimonq2> @acheronuk: trojita is being fun: https://launchpad.net/~lubuntu-ci/+ …], Why I removed it from Kubuntu CI builds
[09:08] <guiverc> :(  fail again sorry on ""Full disk install with encryption on a EFI system without secure boot" using 20190330 daily with ppa:lubuntu-ci/unstable-ci (full-upgrade; logout, login & install)
[09:13] <guiverc> lp report 1822409 updated
[18:10] -lugito:#lubuntu-devel- [T22: Bring those swaps back] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T22#349


[04:40] <kesor> any way to tell upstart it should pickup an existing process?
[04:47] <ion> I’m not sure if one could theoretically do that without a race condition.
[06:44] <kesor> I ended up creating this monster, https://gist.github.com/kesor/6255584#file-unicorn-conf … if anyone sees how it can be improved, it would be great. Since although it works fine, I am not completely happy with it :(
[06:45] <kesor> for example it breaks when sending a reload signal :
[22:44] <axisys> on precise.. how do I start an event after mysqld start ?
[22:44] <axisys> start on event mysql ?
[22:45] <axisys> I am looking for an example.. looking at cookbook.. so that might work.. thought?
[22:45] <axisys> thoughts?
[22:51] <axisys> start on started mysql should work, right?
[23:33] <ion> If the job name is mysql, yes.


[01:52] <lotuspsychje> good morning
[06:03] <lordievader> Good morning
[06:12] <marcoagpinto> Heya
[06:31] <ducasse> good morning
[09:11] <Mekaneck> Allie: looks like they are back in offtopic as vagaj4 and misbehaving again. However they left. Just keep an eye on it please.
[09:17] <Allie> Mekaneck: ah stunning, ban evasion is something i can certainly look into
[09:17] <Mekaneck> thanks :)
[09:18] <Mekaneck> iirc you didn't ban them from #ubuntu-offtopic yesterday but just quieted them. They were banned from #ubuntu however.
[09:19] <Allie> Mekaneck: i shall have drone upgrade the ban if they return on v4
[09:19] <Mekaneck> they are still in offtopic as mundelj
[09:20] <Mekaneck> Allie: roger
[09:20] <Allie> a discussion is being had, since they do seem to be a particularly strong font of drivel.
[09:21] <Mekaneck> they probably used another IP or maybe a proxy to get in offtopic again
[09:21] <Mekaneck> alright
[09:21] <Allie> and whilst it mostly seems they want to make friends, not respecting "go away" is more of a problem
[09:23] <Mekaneck> this isn't acceptable: [03:11:17] <vagaj4> can i put my penis in acetone? [03:11:28] <vagaj4> just want to ask
[09:25] <Mekaneck> Anyway, thanks Allie for looking into it :)
[10:51] <oerheks> Windows 11 is no longer compatible with Oracle VirtualBox, hurray for KVM!
[11:04] <Mekaneck> i don't even care for windows at all
[11:30] <guiverc> Mekaneck, if it wasn't for windows on the wall; I'd not be able to see outside at all.. windows aren't all that bad even if one type is :)
[11:32] <Mekaneck> lol
[11:38] <lotuspsychje> lol
[12:11] <marcoagpinto> lol
[12:11] <marcoagpinto> :)
[12:12] <marcoagpinto> I won't update to Windows 11
[12:12] <marcoagpinto> unless I buy a new laptop that comes with it
[12:26] <Mekaneck> you probably can't upgrade to W11, all depends on your machine if it's compatible and has TPM 2.0
[12:26] <Mekaneck> also they will force you to have a webcam to run W11 in the near future
[12:27] <Mekaneck> i'd switch to linux only if i were you, support for W10 ends in 2025
[12:57] <daftykins> Mekaneck: lol what nonsense are you spreading?
[13:03] <TJ-> presumably https://blogs.windows.com/windows-insider/2021/08/27/update-on-windows-11-minimum-system-requirements-and-the-pc-health-check-app/
[13:04] <TJ-> there's been talk about the minimum hardware requirements being applied to VM guests, and breaking VirtualBox as a result, despite MS saying the minimum hardware requirements do not apply to virtual machines
[13:15] <daftykins> the webcam claim is what i'm considering nonsense
[13:25] <daftykins> certainly some eyebrow raising choices all in all
[13:27] <TJ-> oh, I think that was hyperbole
[13:28] <TJ-> as in 'what next!? webcams?'
[13:29] <daftykins> i don't
[13:30] <daftykins> TJ-: had a fun one the other day, 2.7 kW oven heating element blew mid-cook of fish and chips, took out the power to the whole house :D
[13:30] <TJ-> ouch!
[13:31] <TJ-> we had a Land-Rover burst into flame whilst being driven past the farm last evening; luckily they got out in time but it's melted the lane
[13:31] <daftykins> wowzer
[13:31] <TJ-> I was driving past it to block the lane when a tyre explosed; flames were about 5 metres high at that point
[13:35] <Mekaneck> daftykins: i read the webcam nonsense somewhere a while ago, can't recall where though
[13:36] <daftykins> i have a feeling a lot of the nonsense news will go away after release
[13:57] <leftyfb> I worry about my car bursting into flames almost every day
[15:22] <Mekaneck> Allie: mundelj is active again in #ubuntu-offtopic
[15:23] <Allie> Mekaneck: noted. eyes on them.
[15:23] <Mekaneck> thanks
[16:45] <oerheks> "New malware strain dubbed 'Sanya'. Sanya targets Windows via the Windows subsystem for Linux."...
[16:46] <lotuspsychje> : o
[17:13] <Mekaneck> looks like mundelj also evaded his ban in #linux-offtopic, pinged the Op there about the matter
[17:15] <Mekaneck><EMAIL_ADDRESS>from yester day  and<EMAIL_ADDRESS>from today
[17:15] <hggdh> Mekaneck: they did not, it seems, the ban expired at 14:57 UTC today
[17:15] <hggdh> (at least for today, in #u-offtopic)
[17:16] <Mekaneck> not in linux-offtopic afaik
[17:16] <Mekaneck> and ubuntu-offtopic he wasn't banned, just quieted
[17:16] <hggdh> 4:57:29       -- | Notice(Drone): [#ubuntu-offtopic] Drone sets [#154 -q<EMAIL_ADDRESS>-<EMAIL_ADDRESS>1d 0h 18s]                                                                  │
[17:16] <hggdh>                            │15:09:33       -- | Notice(Drone): [#ubuntu] Drone sets [#155 -b<EMAIL_ADDRESS>-<EMAIL_ADDRESS>1d 0h 27s]
[17:17] <Mekaneck> that wasn't a ban :)
[17:17] <hggdh> indeed
[18:02] <lotuspsychje> !next
[20:19] <Bashing-om> UWN: Issue 701 is on the streets: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue701 :D
[20:20] <daftykins> nice work there, ubottu
[21:23] <goddard> when do the nvidia drivers usually get updated after nvidia releases?
[21:28] <Mekaneck> not
[21:51] <goddard> Mekaneck: sorry?
[21:53] <Mekaneck> they don't get updated on ubuntu unless you use a PPA
[21:54] <Mekaneck> at least that's what i remember from years ago
[21:55] <Mekaneck> if you use the ones from the repo then that's what you get afaik and those won't be updated
[21:55] <sarnold> goddard: it depends upon the series you're using, check the packages
[21:55] <sarnold> https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+publishinghistory
[21:55] <sarnold> https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+publishinghistory
[21:55] <sarnold> https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+publishinghistory
[21:55] <sarnold> ...
[21:56] <goddard> yeah i was looking at that ppa
[21:56] <goddard> looks like it still hasn't released the newest yet
[21:57] <goddard> https://www.nvidia.com/Download/driverResults.aspx/180475/en-us
[21:57] <sarnold> it's not a ppa, it's just the archive
[21:57] <sarnold> goddard: oh nice, a test case that's here and now :)
[22:11] <goddard> what is involved with packaging up the nvidia drivers
[22:12] <daftykins> probably great pain and hair loss
[22:12] <goddard> is nvidia's .run file an archive ?
[22:12] <daftykins> that's a binary
[22:12] <goddard> haha
[22:12] <daftykins> wouldn't recommend version chasing
[22:12] <sarnold> no kidding
[22:12] <sarnold> let our guy do it
[22:13] <goddard> it lets me open it with neovim
[22:13] <goddard> you can put ELF binary data in a shell script?
[22:14] <goddard> 800 lines of shell then a giant ELF
[22:15] <sarnold> sure
[22:15] <sarnold> shar archives were doing that before there was an ELF
[22:16] <sarnold> coverity distributes their gunk that way, and apparently so does nvidia
[22:16] <sarnold> it's not real popular among foss folks but proprietary people seem to love it
[22:16] <daftykins> anything to be different!
[22:16] <daftykins> ;)
[22:20] <goddard> is it some program that packages it for them?
[22:21] <goddard> :q
[22:21] <sarnold> chances are good they wrote it themselves, but yeah
[22:21] <goddard> whoops
[22:22] <goddard> ahh
[22:22] <goddard> probably fun working at nvidia
[22:25] <goddard> love AMD drivers though
[22:25] <goddard> hopefully their next gen cards are better than nvidia
[22:25] <goddard> or maybe Intel will pull a rabbit out of the hat
[22:25] <sarnold> unlikely :)
[22:25] <goddard> ya sadly
[22:25] <sarnold> they're having trouble with CPUs these days, relatively speaking
[22:26] <goddard> but two open source driver companies is cool
[22:26] <sarnold> I mean, I've always looked specifically for intel graphics on my systems because I don't want to deal with the hassle :) but I don't think they come anywhere close to the performance of amd/nvidia
[22:27] <daftykins> nope!
[22:27] <goddard> no and their new graphics are not well supported
[22:27] <goddard> i have a xe 1 or whatever they are calling it in the 11th gen chips and it just not can play doom eternal
[22:28] <goddard> sorry didn't get my license to type yet
[22:28] <goddard> haha
[22:28] <goddard> just NOW can play doom eternal
[22:28] <daftykins> hmm must be at low res, low detail
[22:28] <goddard> doom is pretty optimized but yet only 720p
[22:32] <goddard> works well though with latest kernel and latest mesa


 "Pratham Patel, this is with..." <- Yep, I got the tarballs from kernel.org and ofc verified the signature. After `make olddefconfig`, I do get `CONFIG_RUST=y` from the `.config` file.
[01:16] <thefossguy> Even after booting in the new kernel, I get `CONFIG_RUST=y` from `/boot/config-$(uname -r)`
 "(although all flavours should..." <- Why? Different flavors target different use cases which might have different kernel needs. Ubuntu Studio for example wants the low-latency kernel.
[04:42] <alkisg> juergh: I don't think that was a deliberate choice, I think they just weren't notified to update their seeds
[04:43] <alkisg> When there's a deliberate choice, sure; but e.g. if you ask martin now "does mate deliberately offer a different kernel than ubuntu"? He'll probably answer "wut?" :D
[04:44] <juergh> he. fair enough.
[04:46] <alkisg> So, to sum up my problems are two, (1) why, when someone starts with -generic, they end up getting -hwe with plain updates, and (2) why some of them end up with -oem too, i.e. 3 different kernel series in parallel
[04:47] <alkisg> Since this isn't a known issue, I'll try to investigate the apt logs of affected machines when I next get a chance
[14:28] <Eickmeyer> alkisg: Ubuntu Studio wanting the lowlatency kernel is a deliberate choice.
[14:38] <alkisg> Eickmeyer: yeh, I know about that one