[00:36] <cratos> hello folks. I just installed xubuntu on my acer one netbook. I have a hiddden wireless networkk that the machine doesn't automatically connect to.
[00:36] <cratos> I can click on the network icon,, and say connect to hidden network and it works correctly
[00:37] <cratos> is there a way you guys know to automate this? Any help is appreciated!
[00:51] <writing_novel> Hello, hello, hello! I am just installing Xubuntu and was curious about a few things...
[00:55] <writing_novel> I am curious, the XFCE look seems to be a bit messed up. The Standard XFCE has more a gnome 2 look, what happened to the XFCE is Xubuntu? Why is it messed up?
[00:56] <pleia2> Xubuntu uses alternate theme and setup than Xfce based on user feedback
[00:56] <pleia2> so it's not "messed up" - it's Xubuntu, not Xfce
[00:56] <pleia2> well, not "plain Xfce"
[00:57] <pleia2> if you don't like it you can change it though :)
[03:04] <writing_novel> Ah, okay. How do I change it to the "plain Xfce"?
[03:05] <writing_novel> It is advertised as Ubuntu + Xfce - but I mean, people used to Xfce are expecting a particular look, so, its not surprising people installing it would be like, WTF? its not Xfce.
[03:05] <writing_novel> I realized it was (as a friend had installed it and thought what I just described)
[03:05] <writing_novel> but
[03:05] <writing_novel> I'd prefer to have Xfce if that is what is promised
[03:05] <writing_novel> How do I change it back to its normal Xfce mode?
[03:11] <xyzone> what's different? the menu maybe
[03:12] <writing_novel> the menu is entirely different. At any rate, I'd like to upgrade to the plain XFCE style?
[03:12] <writing_novel> how do I modify it back to real XFCE?
[03:12] <xyzone> edit the menu
[03:12] <writing_novel> I am looking for a how to or that kind of thing not a generalized "just do such and such"
[03:13] <writing_novel> I obviously have no idea how to turn it into a normal XFCE
[03:13] <xyzone> all i'd know is to edit the menu or the skel file
[03:13] <writing_novel> I am not editing anything
[03:14] <writing_novel> I want what comes with XFCE normally
[03:14] <writing_novel> I will find out how to normalize or end up dumping Ubuntu in favor of something with a normal XFCE
[03:14] <xyzone> dump it
[03:14] <writing_novel> I do not want this windows like garbage. I want the Gnome 2 experience that XFCE was originally intended to be like
[03:14] <writing_novel> I might have too
[03:15] <writing_novel> I hoping I find a way to fix it
[03:16] <writing_novel> Anyway I gotta try some other rooms, this one has not turned out to be very helpful
[03:16] <writing_novel> but thanks anyway
[03:21] <Unit193> writing_novel: Log out, and in the session selection select "Xfce" rather than "Xubuntu"
[03:21] <writing_novel> OK! I shall try that.
[03:23] <writing_novel> No go, it has not fixed the issue. Despite doing that I still have this messed up "windows like" menu
[03:23] <writing_novel> it seems not look like the old style Gnome2 Applications menu I expect
[03:24] <Unit193> Seems it's still using Whisker, usually logging into that session gives you stock Xfce.
[03:26] <writing_novel> ok
[03:26] <writing_novel> If Whisker is the weird menu system, then yes, I got Whisker again.
[05:40] <Helios79> Are there any known issues with VIA's (yeah I know, don't remind me how bad they are) P4M890 chipset and version 14.04 of Xubuntu? I get a red cursor instead of the XFCE interface. 12.04 seems to work fine.
[05:48] <gabkdlly> Helios79: Usually, if there are known issues, a web search will usually return them.  But the place where issues are tracked for Ubuntu ( and its derivatives like Xubuntu ) is  https://bugs.launchpad.net
[05:49] <gabkdlly> Helios79: I recommend you search for "P4M890" on launchpad.
[06:07] <Helios79> I'll just stick with 12.04 instead of fighting with a search. Not like support for 12.04 is dropping anytime soon.
[06:28] <gabkdlly> Helios79: Were you booting off of an installation medium ?  Did you verify your installation medium before trying to boot ?
[06:28] <gabkdlly> Helios79: Did you use 14.04.1 ?
[06:36] <gabkdlly> Helios79: What program did you use to create the install medium ?  I usually get the best results with UNetbootin.
[06:38] <Helios79> Imgburn + the media. Debian Wheezy installs fine, 12.04 installs fine, and I've had the same disc work on other configurations.
[06:38] <Helios79> Probably just typical VIA chipset issues.
[06:45] <gabkdlly> Ah, OK.
[06:56] <james0r> man seems like alacarte and menulibre are just buggy as hell on xubuntu 14.04
[06:57] <james0r> most unexpected stuff goes on while trying to do simple stuff
[06:59] <james0r> making a desktop file manually seems to be the only option
[07:02] <james0r> ahh running menulibre as sudo seems to work alright. guess it was just permissions issues.
[07:02] <james0r> in that case editing the menu by using the Whisker context menu is useless.
[09:20] <alket> is there a clean looks theme ?
[09:20] <alket> like it used to be in gnome 2 ?
[09:21] <cfhowlett> alket, there is ubuntu-gnome
[09:21] <alket> cfhowlett, yeah i know , but i like xfce , i just want that theme
[09:23] <cfhowlett> alket, searc www.xfce-look.org
[09:24] <alket> thanks
[09:25] <cfhowlett> alket, happy2help
[10:22] <Umberto54> Salve
[10:22] <Umberto54> Ho un problema di installazioone. Posso chiedere?
[10:23] <cfhowlett> !italian | Umberto54
[10:25] <Umberto54> grazie
[10:34] <Umberto54> quit
[11:35] <sorinello> Hello. Is there an equivalent of Gnome Commander in XFCE ?
[12:06] <HedgeMage> WTF is Gnome Commander?
[12:08] <mchew> Commander of the Gnome Army.
[12:08] <mchew> j/k :)
[12:08] <mchew> It's a file manager.
[12:14] <HedgeMage> Ahh.  I'm more of a CLI type, but I know that Thunar is installed in Xubuntu by default, and spacefm is available in the repos.
[12:16] <elfy> gnome-commander is in the repos
[12:16] <elfy> sorinello: ^^
[13:28] <gatis> Hi how can i delete all Xfce4 pannels?
[13:28] <GridCube> and still use xfwm4?
[13:28] <gatis> yes
[13:28] <gatis> sir
[13:29] <gatis> I like dock :) so i don't need panel
[13:29] <GridCube> >killall xfce4-panel
[13:29] <GridCube> should kill it and still have xfwm4 running
[13:30] <GridCube> you restart the panels using xfce4-panel from alt-f2
[13:33] <GridCube> you can go to settings > session and startup > applications autorun > add a task "killall xfce4-panel"
[13:33] <GridCube> i don't know how to set it up to not launch it in the first place
[13:33] <GridCube> im sure you can tho
[13:36] <GridCube> gatis, in the configuration tool "Configuration editor" you have a setting called xfce4-session, and one of its tasks is xfce4-panel, i would not change my settings but i think thats what you need to edit
[13:44] <gatis> Thanks. I was having dinner
[13:44] <ikonia> gatis: please show me the output of "uname -a"
[13:45] <gatis> ikonia: why?
[13:45] <ikonia> because you are using archlinux
[13:45] <ikonia> not ubuntu
[13:45] <ikonia> and you're using this channel because you've been banned from archlinux and the archlinux offtopic channel
[13:46] <GridCube> i hardly believe that was necesary here
[13:50] <whyameye> I updated from 12.04 to 14.04 and now my screen blanks on timeout very early even though I have shut off screen blanking and the screen saver
[14:06] <Hedgework> check your acpi settings...it's possible that the screen isn't blanking because xscreensaver told it to, but because your power management thinks it's time to save power
[14:09] <whyameye> I just found that xset had a timeout for the screen saver to 60. I assume that's seconds? I wonder what is setting xset? I don't see anything setting it in my sessions/startup. Anyway, I just turned screenblanking off for xset and I'll see if that makes a difference
[14:15] <alan_o> Hi all. I just installed the 14.10 beta and it's outstanding. It required the least amount of tweaking of any desktop distro I've installed in a long time. Keep it up!
[14:17] <elfy> hi alan_o - that's great - what would be even better would be for you to actually report that on the image tracker
[14:17] <elfy> http://iso.qa.ubuntu.com/qatracker/milestones/315/builds - there are xubuntu 32 and 64 bit options at the bottom
[14:17] <elfy> thanks :)
[14:17] <alan_o> ok, will do.
[14:18] <elfy> awesome - I'm having a rather bad time actually getting results on tracker this cycle - as far as I know we've got about 10 installs of 14.10 ;)
[14:31] <alan_o> ok, done. Had to reset password, etc...
[14:38] <elfy> alan_o: thank you :)
[14:38] <animeman> after 15 yrs on windows i dived in and what a learning curve eh
[14:39] <deshipu> animeman: it's way better than 10 years ago
[14:41] <alan_o> So the puzzling thing to me about the xfce project is that development is moving forward (as evidenced by Xubuntu), but there's no indication of it on the xfce website or in the way of official xfce releases. If one went to the xfce website, they would get the impression that it was a stagnating project, with no releases in 2 years. Is there some part of it that I'm missing?
[14:42] <cfhowlett> alan_o, xfce and xubuntu are 2 different things.
[14:42] <alan_o> I read someone say that the Xubuntu and xfce teams are largely the same people and that the code the xubuntu people do does make it into the xfce repos. Is that not true?
[14:42] <cfhowlett> alan_o, and there HAVE been updates to xfce recently and ongoing
[14:42] <Unit193> "Development" releases, Xfce components of 4.11 have had several releases, alan_o.
[14:43] <cfhowlett> alan_o, I've no doubt they share developers, but ... xubuntu = canonical.   xfce is a different entity.
[14:43] <alan_o> hmm ok. so what I read was a bit exaggerated then.
[14:44] <alan_o> Well, development releases I can't argue with. On the main page though, "latest news" says 4.10 released in April 2012.
[14:44] <Unit193> alan_o: Depends on what you mean, Parole, Xfce4-powermanager, and maybe xfce4-settings are taken care of by a couple Xubuntu devs.
[14:45] <cfhowlett> alan_o, peek at the credits.  all kinds of people are involved.
[14:45] <alan_o> no doubt about it.
[14:47] <cfhowlett> alan_o, but you are absolutely right - last update to the main main was 2012.  they could perhaps do a better job of updating their news.
[14:48] <alan_o> Yeah, it's come so far since then. It really is nice.
[15:35] <derek-g> Why do I get this message when trying to mount sshfs share in thunar: "Failed to open / on username@server. The name :1.1025 was not provided by any .service files"
[15:36] <derek-g> I killed all gvfs services - but that didn't help...
[15:36] <holstein> derek-g: i would try mounting manually or with gigolo, and see if i get any errors.. or if the server is up and all that.. up/avialable
[15:38] <derek-g> holstein. hmm. yeah. it opened from gigolo.
[15:39] <derek-g> holstein, it just came up with some error "cache invalid" first time I've tried opening it up from gigolo.
[15:39] <derek-g> holstein, but then it worked - and it now opens from thunar too.. weird.
[15:39] <derek-g> holstein, thanks.
[15:39] <holstein> derek-g: well, gigolo just mounts it.. and then, you can navigate from whatever filemanager
[15:40] <holstein> derek-g: i mean, i like using gigolo, but, that doesnt answer why its not mounting in thunar..
[15:40] <xubuntu914> can¨t play youtube movies no sound en picture
[15:41] <GridCube> xubuntu914, check that pavucontrol is streaming the sound to your desired device
[15:41] <xubuntu914> what
[15:41] <holstein> xubuntu914: try troubleshotting these independent of your system audio.. does audio work otherwise?
[15:42] <xubuntu914> yes radio sound is good
[15:42] <holstein> xubuntu914: what radio?
[15:42] <xubuntu914> 3fm
[15:42] <holstein> xubuntu914: anyways.. i would consider using the flash player in the chrome browser..
[15:42] <GridCube> open pavucontrol, clic on the speaker icon in the panel, go to settings, see in the first tab when playing a video that its sending the sound to the device you want to listen, if its hdmi it should say hdmi, if its analogue it should say that
[15:43] <derek-g> holstein, it's mounting. But then after ssh server get's restarted or if I connect via VPN to some other network - thunar's shortcut get's corrupted or something.
[15:43] <holstein> derek-g: well, it gets unmounted
[15:43] <holstein> derek-g: you may want something more persistent.. samba for example..
[15:43] <holstein> !samba
[15:43] <DJJeff> when choosing a theme in xfce4-appearance-settings it changes for current user
[15:44] <DJJeff> how to change it for the root user
[15:44] <holstein> !root
[15:44] <GridCube> you should never log in as root
[15:44] <derek-g> holstein, yeah. these boxes I can only ssh in - can't install smaba on them.
[15:44] <holstein> DJJeff: you should not have, and dont want a root user
[15:44] <DJJeff> I launch wireshark as root
[15:44] <derek-g> holstein, but that's ok- imho gigolo should work for me.:)
[15:45] <DJJeff> because its need
[15:45] <holstein> derek-g: i like the tool.. and that might the be best/easiest for you, since you cant do much server-side
[15:45] <DJJeff> and the menus in a application started with gksu are ugly
[15:45] <holstein> DJJeff: you should be able to specifiy whatever settings you want the application to have.. gksudo appplication-name -flags-for-themeing
[15:46] <DJJeff> theme files go into /usr/share/themes right?
[15:47] <holstein> DJJeff: you dont have a root user, so you cant just apply a theme to that account that is not there, and shouldnt be used
[15:47] <knome> or /home/.themes/ for single-user use; you can get more information in the docs..
[15:47] <holstein> DJJeff: i would just look into launching the application with an argument about a theme to use
[15:47] <DJJeff> not all apps support choosing a theme
[15:48] <DJJeff> making it system wide makes sense
[15:52] <holstein> DJJeff: http://askubuntu.com/questions/57990/set-a-specific-theme-for-root-launched-applications is where i would start..
[15:53] <DJJeff> it states that root apps use the theme of the user that starts the app
[15:54] <DJJeff> great link though
[15:54] <holstein> DJJeff: if the root app you were using used the theme of your user, you'd be fine then, correct?
[15:55] <DJJeff> yes
[15:55] <holstein> DJJeff: i thought you were asking becuase the theme is *not* being used from your user? this link states where to create the files in the locations that knome was suggesting that the root launch should use
[15:56] <DJJeff> like in xfce4-appearance-settings I choose a theme for my normal user account say (Greybird)
[15:56] <DJJeff> and I do gksu wireshark
[15:56] <DJJeff> wire should also use (Greybird)
[15:56] <DJJeff> wireshark*
[15:57] <holstein> sure, i understand that .. but thats not what will happen, since you are running that as a different user.. the link i gave explains how to specifiy a theme for the gksu lanuch
[15:58] <holstein> i would read from "I found a hack to get get a system wide change :)
[15:58] <holstein> read from there to the end of the page..
[15:58] <DJJeff> I guess it would also depend if the application is gtk2 gtk3 or qt
[15:59] <DJJeff> and if my theme supports all 3
[15:59] <holstein> DJJeff: then, you will change what you need accordingly..
[15:59] <knome> if you have installed a theme in your home folder, applications ran with gksudo will not use the theme, unless it's *also* available in /usr/share/themes
[16:00] <DJJeff> most of the time newer themes are backwards compat and support all 3
[16:01] <holstein> DJJeff: then, just link to one you want that suits your needs, and put it where it needs to be
[16:01] <DJJeff> will do
[17:25] <joppe82> anybody knows is it possible to install acestream player to xubuntu 14.04
[17:26] <bazhang> !info acestream
[17:26] <bazhang> from where
[17:30] <joppe82> its on 13.04 repo but no 14.04
[17:31] <joppe82> its an app to watch live sport streams
[17:31] <bazhang> !find acestream
[17:31] <bazhang> PPA?
[17:32] <joppe82> nope
[17:32] <bazhang> compile it then I suppose
[17:32] <joppe82> im a noob :)
[17:32] <brainwash> or contact the package maintainer
[17:33] <bazhang> find another app then
[17:37] <joppe82> just switched from win 7 to linux, lot to learn
[17:39] <brainwash> feel free to join the offtopic channel if you want to talk about general stuff
[17:39] <brainwash> !ot
[17:40] <enkienlil> hello all, I have been trying to use the program APTonCD, although it creates an ISO K3B burns a coaster, it fails at 98.2%, any ideas?
[17:41] <brainwash> !k3b
[17:42] <brainwash> it's a KDE app, sadly I'm not familiar with it
[17:43] <enkienlil> I'm using Xubuntu 14.04 with standard desktop, I found the program in software manager.
[17:44] <enkienlil> supposed to be the bees-knees for backups :/
[17:44] <brainwash> that's fine, I suggest that you ask in #ubuntu and #kde also
[17:44] <brainwash> xubuntu does not ship any KDE applications by default
[17:45] <enkienlil> It was in software manager?
[17:45] <brainwash> so, supporting them here is a bit tricky
[17:45] <brainwash> you can find everything in the software manager
[17:45] <enkienlil> troo
[17:46] <brainwash> but the people in this channel usually use Xfce/Xubuntu specific software
[17:46] <brainwash> you can try to burn the iso with xfburn
[17:46] <brainwash> it's Xfce own burning tool
[17:46] <enkienlil> Now there's a problem
[17:47] <enkienlil> when I set the burn speed to x4 it still burns at max speed
[17:47] <brainwash> in xfburn?
[17:47] <enkienlil> ...is why I used K3B
[17:47] <enkienlil> yer
[17:47] <brainwash> oh, mmh, maybe worth reporting it as bug on launchpad
[17:48] <enkienlil> will do...something is definitely going wrong somewhere
[17:51] <joppe82> well another question, how can i prevent xubuntu to go log off mode when i am not in the computer, because i use remote desktop from my ipad.. when xubuntu goes  log off mode i can not connect
[17:55] <brainwash> joppe82: does it log out or only lock the screen? the login and unlock screens look very similar
[17:56] <brainwash> you can disable screen locking via settings manager > light locker settings
[17:56] <joppe82> ok thanks
[19:26] <hoijui> i have compiz running on xubuntu 14.04. it reopens the previously open applications after reboot, but all on the first screen, instead of on their original ones. how to fix this?
[19:28] <holstein> i bet it does.. i suggest not using compiz in xfce as a "fix".. other than that, is it happening with another user?
[19:32] <hoijui> holstein... ok.. i did not try an other user yet
[19:33] <hoijui> i use compiz because of the scale and expo effects only, but thye are the best way i have seen so far for navigating between windows
[19:33] <hoijui> though you are right.. it has other bugs too
[19:33] <holstein> you should consider other compositor options.. i find/found that compiz in ubuntu is closely related to unity, and, is problematic to implement in xfce, at best
[19:34] <hoijui> even with these two things i use, it has multiple problems (cant combine expo and scale (not anymore, worked a few years ago)
[19:34] <hoijui> mmm
[19:34] <holstein> sure.. a few years ago, it wasnt so closely tied to unity
[19:34] <hoijui> can you suggest anything wiht a nice way to switch between windows?
[19:34] <hoijui> mm
[19:35] <holstein> hoijui: TBH, i just use the xfce one.. but, there are other options.. you'd just have to check them out.. really depend on what you want
[19:35] <hoijui> i still see many of the new things in linuxworld as a way to hinder it
[19:35] <hoijui> ok
[19:35] <holstein> compton?
[19:42] <hoijui> thanks holstein.. will look around, and check that one out too
[20:01] <hoijui> i am going to give "awesome" a try. in the description of features i saw one thing that could seal the deal for me: windows are tagged, adn screens can show multiple tags, and tags can be shown on multiple screens
[20:48] <joppe82> good night and thanks for your help
[21:31] <m3n3chm0> hello, chromium crash since today :S url_request.cc(709)] Trying to send secure referrer for insecure load
[21:44] <knome> m3n3chm0, then file a chromium bug in launchpad
[21:45] <m3n3chm0> ?¿
[21:46] <knome> if you have a bug with chromium, file it on launchpad
[21:46] <m3n3chm0> you mean it's a bug since today on this bug on launchpad opened ?
[21:47] <knome> i'm not following you.
[22:29] <writing_novel> snuffeluffegus: You have badly mutated the spelling of Aloysius'  informal name, it is spelled: snuffleupagus
[22:30] <writing_novel> (last name)
[22:33] <snuffeluffegus> woa
[22:34] <snuffeluffegus> Yeah I know
[22:34] <snuffeluffegus> It's a play on an afk nickname
[22:35] <knome> guys... we have #xubuntu-offtopic for general chatter ;)
[22:37] <snuffeluffegus> oo sry
[22:37] <knome> that's fine ;)


[11:02] <ogra> and ldm got dropped from the edubuntu CD since gdm already provides x-display-manager ...
[11:02] <ogra> crazy bug ...
[11:03] <ogra> Kinnison, on ltsp as well please
[11:03] <Kinnison> one at a time eh?
[11:04] <ogra> yeah ....
[11:04] <ogra> but espresso and ltsp are flight 4 stuff ...
[11:08] <Kinnison> I've just unstuck all the builders
[11:08] <Kinnison> all but i386 were marked failed
[11:08] <Kinnison> probably internal network hiccough in the DC
[11:10] <ogra> yup
[11:10] <ogra> its a bad time for preparing a flight release ...
[11:10] <ogra> but looks like we're nearly done ...
[11:11] <ogra> i had surely none yet that was this tricky to prepare ...
[11:13] <Kinnison> Yes it's just unfortunate
[11:14] <Kinnison> this DC move has caused/exposed issues
[11:16] <ogra> yup
[11:17] <ogra> but it puts extra pressure on elmo and Znarl as well ... thats sad ...
[11:17] <Kinnison> The buildd master should be able to recover from this situation
[11:17] <Kinnison> I've proposed a way to recover
[11:17] <Kinnison> we just need to code it
[11:21] <ogra> Kinnison, you didnt reject bug 31822 ?
[11:21] <Ubugtu> malone bug 31822 in gnome-power-manager "Please restore suspend lid action" [Normal,Unconfirmed]  http://launchpad.net/bugs/31822
[11:22] <Kinnison> I didn't reject it because personally I don't agree with upstream's decision
[11:22] <Kinnison> we'll see what happens when I punt users at that bug in gnome
[11:23] <Kinnison> if upstream stick by their decision then I'll reject the bug
[11:23] <ogra> yup
[11:25] <Burgwork> Kinnison, as long as resume is fast from suspend, there is no reason why we shouldn't suspend all the time
[11:25] <Kinnison> Burgwork: there's a very good reason
[11:25] <Kinnison> Burgwork:  you may have a process which is actively talking to the network
[11:25] <Kinnison> Burgwork: suspending would fuck that up
[11:25] <Kinnison> personally I never suspend on lid action
[11:25] <Kinnison> because I think that's crackful
[11:25] <Kinnison> but hey :-)
[11:26] <ogra> me too
[11:26] <Burgwork> Kinnison, if you have a running process, why are you closing the lid?
[11:26] <ogra> i want my mail to still be delivered
[11:26] <Kinnison> Burgwork: maybe I'm about to get up and walk from one room to another
[11:27] <Kinnison> Burgwork: maybe I'm closing the lid so as to not be distracted while someone speaks to me
[11:27] <Kinnison> Burgwork: I can think of a bajillion reasons
[11:27] <Burgwork> yes, but the most common I suspect is to carry it around
[11:27] <Kinnison> indeed
[11:27] <Kinnison> and I don't want to drop off irc while I move from room to room
[11:27] <Burgwork> and then you do want to suspend, as you are not using it
[11:28] <Burgwork> that is a bug in the irc client, imho
[11:28] <Kinnison> what? it's a bug in the irc client that you've disconnected it from the network so it can't talk?
[11:28] <ogra> heh
[11:28] <Burgwork> Kinnison, no, that it didn't come back from suspend
[11:28] <Kinnison> that's like saying "It's a bug in linux that it doesn't run updatedb while the computer is off"
[11:28] <Kinnison> Burgwork: TCP timeouts
[11:29] <Kinnison> yes
[11:36] <ogra> thanks for speeding up ltsp :)
[11:37] <Kinnison> y'welcome
[11:41] <typonaise> does anybody know what happened to the debian/ubuntu-hardened project and where trulux and company hang out now?


[09:27] <[reed]> asac: any other bugs/patches?
[09:27] <[reed]> :)
[09:29] <armin76> mozilla bug 3
[09:29] <armin76> ! :)
[09:29] <DarkMageZ> mozilla bug #3
[09:30] <DarkMageZ> oh, our favorite bot is gone :(
[09:35] <asac> [reed]: i have another ... and another ... and another :)
[09:35] <[reed]> :p
[09:36] <asac> any idea when beta 3 is planned?
[09:41] <asac> [reed]: would you be willing to help us (distributors) to checkin the security backports we have on 1.8.0 branch (given that i get approval from branch drivers)?
[09:42] <[reed]> Firefox 3 Beta 3 -- http://wiki.mozilla.org/Releases/Firefox_3.0b3
[09:42] <[reed]>  Proposed Schedule
[09:42] <[reed]> The following proposed schedule assumes no re-spin.
[09:42] <[reed]>     * Tree closure: January 22
[09:42] <[reed]>     * Code freeze: January 25
[09:42] <[reed]>     * Build starts: January 28
[09:42] <[reed]>     * QA/Testing starts: January 28/29
[09:42] <[reed]>     * Final release: 1.5 weeks later (or so)
[09:42] <[reed]> asac: sure
[09:43] <asac> great ... stay tuned :)
[09:44] <[reed]> and then you'll nominate me for the sg? :)
[09:44] <[reed]> :p
[09:44] <asac> hehe ;)
[09:44] <[reed]> I'm in the other two Mozilla security groups except for the main one ;)
[09:45] <[reed]> s/except for/but not/
[09:45] <asac> which are the other two?
[09:46] <[reed]> webtools-security (deals with all webtools, websites, and bugzilla) and update-security (deals with addons.mozilla.org)
[09:49] <armin76> mozilla bug 3
[09:49] <armin76> mozilla bug 60
[09:49] <armin76> bah
[09:59] <DarkMageZ> mozilla bug #60
[09:59] <DarkMageZ> !ubotu
[09:59] <ubotu> I am ubotu, all-knowing infobot. You can browse my brain at http://ubotu.ubuntu-nl.org/factoids.cgi - Usage info: http://wiki.ubuntu.com/UbuntuBots
[09:59] <DarkMageZ> bug #60
[10:00] <ubotu> Launchpad bug 60 in baz "buildcfg should be runnable from anywhere" [Wishlist,Confirmed] https://launchpad.net/bugs/60
[10:00] <DarkMageZ> mozilla bug #60
[12:07] <asac> damn provider
[13:52] <asac> @time
[13:52] <ubotu> Current time in Etc/UTC: January 10 2008, 13:52:21 - Current meeting: Desktop Team Development
[13:52] <asac> @time CET
[13:52] <ubotu> Current time in CET: January 10 2008, 14:52:24 - Current meeting: Desktop Team Development
[13:56] <asac> @time GMT
[13:57] <armin76> heh
[13:57] <armin76> same as UTC :P
[14:04] <asac> armin76: thanks for the advice :)
[16:28] <asac> anyone has a fedora install at hand :) ?
[19:16] <armin76> [reed]: i have a bug!
[19:19] <[reed]> armin76: yay
[19:19] <[reed]> did you get some antibiotic for your bug?
[19:19] <[reed]> :p
[19:19] <armin76> int.locale.matchOS sucks! fix
[19:20] <armin76> asac: ^^^
[19:20] <armin76> if matchOS is set true globally, but the user sets in his profile false and specifies a locale, it doesn't work
[20:03] <asac> armin76: he?
[20:03] <asac> armin76: where is the UI to select the locale in ffox 3?
[20:03] <asac> is there any at all?
[20:05] <armin76> there isn't
[20:15] <jcastro> Ubulette_: around?
[20:34] <gnomefreak> im back for a little while on meds atm still l9ots of pain
[20:36] <gnomefreak> is it just me or is mozilla* broken (thinking nss is broken)
[20:40] <gnomefreak> thats assuming ssl is provided by nss or nspr
[20:48] <asac> gnomefreak: hooray!
[20:48] <gnomefreak> ;)
[20:48] <asac> thank god that you feel at least good enough to be here
[20:49] <gnomefreak> yeah for a llittle bit atleast
[20:49] <gnomefreak> looking for sourse of ssl issue atm :(
[20:49] <asac> are you hardy?
[20:50] <gnomefreak> yeah
[20:50] <gnomefreak> gutsy works fine
[20:52] <asac> no issues here
[20:52] <asac> epiphany? or ffox?
[20:52] <asac> epiphany has issues
[20:53] <gnomefreak> ff seamonkey 2 and 1.1.x
[20:53] <gnomefreak> tbird as well
[20:53] <gnomefreak> says ssl is disabled
[20:54] <gnomefreak> maybe hd space but i doubt it prolly just a messed up profile
[21:05] <gnomefreak> not profile :(
[21:08] <gnomefreak> what is the command to look at hd space its not fstab from what i can tell
[21:13] <gnomefreak> ok its not hd space either that is at 10 gigs left. so the warning i get tells me to check profile and hd space
[21:16] <gnomefreak> !info libnss3 hardy
[21:16] <ubotu> Package libnss3 does not exist in hardy
[21:18] <gnomefreak> is it possible its due to ppa version of mspr?
[21:25] <asac> libnss3 is old
[21:25] <asac> its libnss3-1d
[21:26] <asac> you should upgrade everything
[21:26] <asac> lot has changed in hardy
[21:28] <gnomefreak> yeah i saw
[21:28] <gnomefreak> downgrading mspr to hardys version
[21:29] <gnomefreak> there is no libxul-1.9 in hardy?
[21:31] <gnomefreak> damn
[21:37] <asac> libxul-1.9 why?
[21:37] <gnomefreak> not really
[21:37] <gnomefreak> search doesnt find it
[21:41] <gnomefreak> maybe its the reason xulrunner-1.9 is being held back (although i thought xulrunner built libxul
[21:47] <gnomefreak> Alert im getting is "Could not intialize the browsers security component. The most likely cause is problems with files in yout browser's profile directory. Please check that this directory has no read/write restrictions and your hard drive is not full or close to full, It is recommended that you exit the browser and fix this problem. If you continue to use this browser session, you might see incorrect browser behaviour when acces
[21:47] <gnomefreak> i dont see why im getting it unless 10 gigs isnt enough
[21:50] <gnomefreak> Galeon, kaze, work fine only getting alert on ff <IP_ADDRESS> atm i have to install epipahany to test. ff3.0 isnt opening at all atm
[21:51] <gnomefreak> oh yeah tbird also gives alert since it uses ssl to connect to pop i cant download messages
[21:51] <gnomefreak> gnomefreak@Gutsy:~$ firefox-3.0
[21:51] <gnomefreak> Could not find compatible GRE between version 1.9b2pre and 1.9b2pre.
[21:54] <gnomefreak> seems ppa has older version of firefox-3.0 and it doesnt upgrade to b3 in hardy
[21:56] <gnomefreak> yep apt thinks firefox3.0b3 is lower version than ppa b2
[22:00] <gnomefreak> ff-3.0 works fine too
[22:01] <gnomefreak> ok everything tested oinly firefox <IP_ADDRESS> and tbird <IP_ADDRESS> in hardy give me that alert
[22:13] <gnomefreak> firefox isnt building ~/.mozilla
[22:14] <gnomefreak> now it did
[22:20] <gnomefreak> what does firefox-3.0 name bookmarks.bak and .html? moving bookmarks.bak and .html doesnt work in 3.0 to build bookmarks in toolbar
[22:21] <gnomefreak> ah fixed it i had to use import
[22:34] <gnomefreak> ok building seamonkey to upgrade what i have with newest dec. build im gonna leave nick in here for a while but i wont be here i need to lay back down due to pain
[22:50] <gnomefreak> or not
[22:52] <gnomefreak> asac: where did mozilla-devscripts go in hardy sm2.0 depends on it
[22:59] <gnomefreak> i found it in ppa
[23:13] <Ubulette_> hi
[23:14] <gnomefreak> hi
[23:14] <Ubulette> gnomefreak, glad you're back
[23:14] <gnomefreak> for now
[23:14] <gnomefreak> still hurts like shit
[23:14] <Ubulette> happy new year !
[23:14] <Ubulette> oh
[23:14] <Ubulette> too bad
[23:14] <gnomefreak> happy new year ;)
[23:14] <Ubulette> thx
[23:14] <Ubulette> jcastro, pong
[23:15] <gnomefreak> ok im going to lay down looks like i got all build-deps figured out
[23:16] <Ubulette> gnomefreak, mozilla-devscript is just mozclient nicely packaged. it's still in NEW-src. Take the one from bzr or from my ppa
[23:18] <Ubulette> i have another script in mind for a future version


 I'm doing fine but not really as exciting things as you, trying to make sure things are delivered on time currently
[07:26] <zyga-mbp> serious things are meant to be like that
[07:26] <zyga-mbp> I'm very happy to see you and samuele manage snapd
[07:52] <mup> PR snapd#10888 closed: tests: support running all spread tests with experimental features <Created by stolowski> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10888>
[08:02] <mardy> 'morning zyga-mbp
[08:03] <zyga-mbp> hey mardy :)
[08:08] <mardy> find squashfs-root/ -name configure
[08:09] <mardy> squashfs-root/hooks/configure
[08:09] <mardy> squashfs-root/meta/hooks/configure
[08:09] <mardy> squashfs-root/snap/hooks/configure
[08:09] <mardy> I guess I'll edit all of them :-D
[08:10] <zyga-mbp> woah
[08:10] <zyga-mbp> that's a lot of hooks :)
[08:10] <zyga-mbp> technically snapd needs meta/hooks/
[08:10] <zyga-mbp> snap/hooks is probably (guessing) from snapcraft
[08:10] <zyga-mbp> the top-level is dunno
[08:11] <mardy> zyga-mbp: thanks, I'll ask the developers of the snap to do some housecleaning :-)
[08:13] <zyga-mbp> at least configure is not a directory :)
[08:13] <zyga-mbp> that would confuse snapd
[08:13] <mardy> or a socket ;-)
[08:39] <miguelpires> mvo: hi, can you merge https://github.com/snapcore/snapd/pull/10875 please?
[08:39] <mup> PR #10875: client: fail fast on non-retryable errors <Simple 😃> <Created by MiguelPires> <https://github.com/snapcore/snapd/pull/10875>
[08:41] <miguelpires> ty
[08:42] <mup> PR snapd#10875 closed: client: fail fast on non-retryable errors <Simple 😃> <Created by MiguelPires> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10875>
[09:00] <mborzecki> mvo: hi, do you have the source tarballs to pus on the github releases page?
[09:05] <mvo> mborzecki: for 2.53? not yet, sry! I can upload after the meeting
[09:07] <mborzecki> mvo: that's fine, i'll update the arch and opensuse packages when the sources are available
[09:23] <mvo> mborzecki: yeah, sry again, will get to it later but in meetings this morning
[09:43] <mborzecki> got an errand, back in 1,5h or so
[10:21] <mvo> mborzecki: tarfiles updated
[11:02] <mborzecki> re
[11:02] <mborzecki> mvo: thanks!
[11:14] <mardy> mvo: we have a tests/smoke/ directory, should I move the microk8s test there?
[11:21] <mborzecki> meh lxd broke tests https://paste.ubuntu.com/p/2nsXcy5Fyg/
[11:28] <mvo> mardy: the name is a bit misleading, that testsuite is really for smoke testing snapd itself and it is expected to be quick(ish)
[11:29] <mvo> mardy: maybe I should document this :/
[11:38] <mup> PR snapd#10827 closed: fde: add new device-setup support to fde-setup <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10827>
[11:38] <mup> PR snapd#10830 closed: gadget: add `encryptedDevice` and add encryptedDeviceLUKS <Simple 😃> <Skip spread> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10830>
[11:38] <mup> PR snapd#10854 closed: spread: use `bios: uefi` for uc20 <Simple 😃> <Skip spread> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10854>
[12:01] <mup> PR snapcraft#3588 closed: snap: patch patchelf on riscv64 (CRAFT-566) <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3588>
[13:08] <mup> PR snapd#10896 opened: tests: remove "features" from fde-setup.go example <Simple 😃> <Run nested> <Created by mvo5> <https://github.com/snapcore/snapd/pull/10896>
[13:22] <ogra> mwhudson, are you still doing console-conf ? i'm running into a weird bug here ... after installing network-manager on a fully set up UC20 the screen shows "<no ip address>" afterwards while the device actually *does* have an IP ... does console-conf not simply use "ip addr" to find the default IP ?
[13:23] <zyga-mbp> mvo pedronis is not around today?
[13:23]  * zyga-mbp mvo I ran into an issue where snapd cannot remove the core snap (on focal) because it's a part of the model
[13:23] <zyga-mbp> but on classic that is mostly meaningless
[13:24] <zyga-mbp> and it's also a very confusing error message, models are relatively unknown to general public
[13:24] <zyga-mbp> is this by design?
[13:24] <zyga-mbp> The exact interaction is:
[13:25]  * zyga-mbp $ sudo snap remove core
[13:25]  * zyga-mbp error: cannot remove "core": snap "core" is not removable: snap is used by the model
[13:32] <ogra> mwhudson, ah, ian pointed me to https://bugs.launchpad.net/subiquity/+bug/1898583 (which is sadly still not fix-released thanks to core20 stable not having been updated since april (!!!))
[13:32] <mup> Bug #1898583: console-conf with wlan connection does not ever report ip via tty message, even though it does have ip <uc20> <subiquity:Fix Committed> <https://launchpad.net/bugs/1898583>
[13:36] <dbungert> ogra: this one may also be relevant LP: #1903050
[13:36] <mup> Bug #1903050: consoleconf main is broken (core22) <core22> <fr-896> <uc22> <subiquity:Fix Released> <https://launchpad.net/bugs/1903050>
[13:38] <ogra> dbungert, well, it is fixed in core20 candidate (just confirmed) ... the shocking bit is that core20 has not been released to stable since april ... which means there might be a gazillion open CVEs out there on devices 😞
[13:38] <ogra> that bug is for UC22 ...
[13:39] <ogra> (which is still a year away, luckily 🙂 )
[13:42] <ogra> oh, weird ... after the switch to candidate snap info core20 shows something completely different for the stable channel ... the stable image i downloaded had an april-released core20
[13:42] <ogra> (and did not see an update for it with snap refresh)
[13:45] <mvo> zyga-mbp: in a meeting but pedronis should be around
[13:46] <zyga-mbp> perhaps not on irc
[13:46] <mvo> ogra: snap info core20 shows july which is not much better but a bit
[13:46] <mvo> ogra: I think sil2100 knows when core20 is promoted to stable, I expect RSN
[13:47] <ogra> mvo, yeah, this is really weird, i am on a freshly installed UC20 stable image where snap list showed "core20  20210429  1030  latest/stable  canonical✓  base" even after several snap refresh runs that i manually did ... switching the channel to candidate and back for core20 now gives me the correct one
[13:48] <mvo> ogra: oh, that is odd. what image did you use, I would love to test this
[13:48] <ogra> http://cdimage.ubuntu.com/ubuntu-core/20/stable/current/ubuntu-core-20-arm64+raspi.img.xz
[13:48] <ogra> on a Pi4
[13:48] <mvo> ogra: ta
[13:49] <sil2100> We are phasing out core20 right now
[13:50] <zyga-mbp> sil2100 phasing out as in replacing it with something or phase upgrade?
[13:50] <sil2100> We're using automated progressive releases for core20, and it's being phased out right now - the new version that is
[13:50] <mvo> nice
[13:50] <sil2100> But yeah, 20210429 seems like something VERY old
[13:50] <mvo> ogra: there you go, I guess the phasing is the reason you did not get hte update
[13:50] <sil2100> So that shouldn't have been listing at all
[13:51] <ogra> mvo, ah, okay ... though april still seems a bit oldish for the image (which has an image timestamp from june)
[13:52] <ogra> i'd have expected a newer core20 on that image
[13:52] <mvo> ogra: I think we had this big jump https://people.canonical.com/~mvo/core20-changes/html/stable/
[13:53] <ogra> oha !
[13:53] <ogra> okay
[13:53] <mvo> ogra: I guess we need to make sure to keep an eye on this and make sure we release more often
[13:53] <ogra> yeah, we need to make sure CVEs are closed in time 🙂
[13:54] <ogra> else i'll have some customers with torches and pitchforks showing up at my doorstep i fear
[13:55] <mvo> +100
[13:56] <ogra> nah, i dont want more than 100 customers with pitchforks 😛
[13:56] <ijohnson[m]> -95
[13:56] <ijohnson[m]> 5 customers with pitchforks seems like a reasonable bunch to manage
[13:56] <ogra> yeah, 5 i can handle with a garden hose
[13:56] <mvo> hahaha
[14:16] <flotter> Following HACKING.md to go build snap: I feel like I am missing something, as I have two broken deps. (1) secboot - which I was able to bypass with a -tag and (2) dbus *Match* functions, which does not appear to exist in godbus. Any hints - sorry im new
[14:16] <mborzecki> invoking `/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so --library-path /snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu /snap/snapd/current/usr/bin/mksquashfs` fails on opensuse
[14:17] <mborzecki> the usual: libgcc_s.so.1 must be installed for pthread_cancel to work
[14:17] <ijohnson[m]> bboozzoo: hey funny you mention ld
[14:17] <ijohnson[m]> I just pinged you on MM about libc haha
[14:17] <mborzecki> fwiw i think we should not invoke the tooling mksquashfs in tests
[14:17] <ijohnson[m]> I think we need another change to the snap-confine profile for s390x
[14:18] <flotter> GOFLAGS='-tags=nosecboot' go build -o /tmp/snap github.com/snapcore/snapd/cmd/snap
[14:19] <flotter> fdo.go:127:18: undefined: dbus.MatchOption
[14:41] <mborzecki> flotter: is this a new checkout? go.mod should already mention the right version of go-dbus
[14:42] <mborzecki> and that version should have been fetched when go build was invoked
[14:42] <flotter> I did find the functions exist in the downloaded godbus repo
[14:42] <flotter> I did a fresh go get, an hour ago
[14:44] <flotter> go: extracting github.com/godbus/dbus v4.1.0+incompatible
[14:45] <flotter> The name is not very inspiring :D
[14:45] <flotter> The name is not very inspiring :)
[14:47] <flotter> work/pkg/mod/github.com/snapcore/snapd@v0.0.0-20210902070205-9fe87efa1b36/desktop/notification/fdo.go:127:18: undefined: dbus.MatchOption
[14:48] <zyga-mbp> flotter that's not right
[14:48] <zyga-mbp> you should not do that manually
[14:48] <zyga-mbp> go build ./... should do it
[14:48] <zyga-mbp> you're not supposed to compete with go.mod by checking out things by hand
[14:48] <zyga-mbp> here you are running into module versions that use a somewhat elaborate scheme, snapd uses /v5
[14:49] <zyga-mbp> flotter git clone && go build ./... should be enough
[14:49]  * zyga-mbp (apart from C world)
[14:50] <flotter> I only did the go get command (from HACKING.md) and then "GOFLAGS='-tags=nosecboot' go build -o /tmp/snap github.com/snapcore/snapd/cmd/snap"
[14:50]  * zyga-mbp most likely hacking is stale
[14:50] <zyga-mbp> it predates go-mod days
[14:50] <flotter> understood
[14:51] <flotter> so you are saying just check out the git, and build
[14:51] <zyga-mbp> yes, at least that's the start
[14:51] <zyga-mbp> once you check out _and_ are on a debian-like distro you can apt-get build-dep .
[14:51] <zyga-mbp> to get C world side
[14:51] <zyga-mbp> you will be much closer to being able to iterate
[14:51] <flotter> OK let me try, thanks!
[14:52] <zyga-mbp> send patches to fix HACKING.md
[14:52] <flotter> I will do!
[14:52]  * zyga-mbp loves the go.mod world where $GOPATH/src is gone
[14:53]  * zyga-mbp thank you :)
[15:09] <mup> PR snapd#10897 opened: osutil: ensure parent dir is opened and sync'd <Created by MiguelPires> <https://github.com/snapcore/snapd/pull/10897>
[15:17] <mup> PR core20#116 closed: hooks: adjtime: add adjtime file to etc <question> <Created by stulluk> <Closed by stulluk> <https://github.com/snapcore/core20/pull/116>
[15:34] <mup> PR snapd#10896 closed: tests: remove "features" from fde-setup.go example <Simple 😃> <Run nested> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10896>
[15:37] <dbungert> so the LP: #1943077 saga continues - I'm trying to judge if snapd from the deb having problems with `snap pack` is release critical for impish.  Retesting adt with snapd from impish-proposed still shows the problem with libgcc.
[15:37] <mup> Bug #1943077: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s <impish> <rls-ii-incoming> <update-excuse> <snapd:Fix Committed> <openssh (Ubuntu):New> <squashfs-tools (Ubuntu):New> <https://launchpad.net/bugs/1943077>
[15:39] <mup> PR snapd#10881 closed: tests: merge coverage results <Skip spread> <Created by mardy> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10881>
[17:17] <flotter> Hi. GOOS=linux GOARCH=arm64 go build -v -a -o /tmp/build/arm64 ./...
[17:17] <flotter> I am attempting to cross compile snapd for arm and arm64.
[17:19] <flotter> I get a compiler failure for golang-evdev - undefined: ioctl
[17:19] <ijohnson[m]> flotter: golang-evdev is only necessary for building snap-bootstrap which is only used on Ubuntu Core so you should just skip building that binary
[17:20] <dbungert> ijohnson[m]: may I get your thoughts on the matter above?
[17:20] <ijohnson[m]> dbungert: sorry I missed your message above let me re-read the bug again
[17:21] <dbungert> buried in bot updates :)
[17:23] <ijohnson[m]> yeah it gets annoying since the links get expanded and so I don't see individual messages as clearly, meh communication is hard
[17:24] <flotter> If I do want to build the snap-bootstrap, any tip(s) on what I should be looking at to get the deps resolved?
[17:29] <ijohnson[m]> flotter: you need to setup a C cross compiler and use it when compiling, something like this
[17:29] <ijohnson[m]> oh hmm I don't seem to have that in my bash history anymore, darn
[17:34] <ijohnson[m]> flotter: this is what you want essentially
[17:34] <ijohnson[m]> CC=aarch64-linux-gnu-gcc GOARCH=arm64 CGO_ENABLED=1  go build -o snap-bootstrap-arm64 ./cmd/snap-bootstrap/
[17:35] <ijohnson[m]> dbungert: so the situation really hasn't changed at all on our side as it pertains to snap pack and impish, one wrinkle that I wasn't aware of (or more accurately I had forgotten) is that `snap pack` will always unconditionally attempt to re-exec to use mksquashfs from the core/snapd _snaps_ even when the version of snapd itself from the debian package is newer. This is to ensure that snaps that are created are always created with a
[17:35] <ijohnson[m]> supported and working mksquashfs
[17:36] <ijohnson[m]> so this means that we need to have the fix you landed in the snapd/core snaps before it can work in these autopkgtests
[17:36] <ijohnson[m]> and also that any impish users who try to use `snap pack` from i.e. snapcraft will be broken and it won't work until the core/snapd snaps are updated
[17:37] <dbungert> that part I'm not so wild about, but I don't have a feel for how common it would be
[17:37] <ijohnson[m]> unfortunately, while the fix is in the pipeline as part of snapd 2.52.1, it is probably 2 weeks away now I think from going to stable for all users to be able to get that fix
[17:39] <ijohnson[m]> we have 2.52 ready to go to stable very shortly, and the next release after 2.52 will be 2.52.1, but we need to let 2.52.1 bake a bit in the beta channel before we can push it through
[17:40] <ijohnson[m]> and in the meantime, real users trying to use snapcraft on impish can use the edge (possibly beta) channel of the snapd snap until the fix has made its way through the pipeline
[17:42] <flotter> Thank you very much, understood
[17:43] <ijohnson[m]> dbungert: does that make sense?
[17:43] <dbungert> It does, yes.  The real question here is - do we believe action needs taken prior to impish release, and I think the answer is "no".  We plan to point affected people to snapd edge/beta.
[17:44] <ijohnson[m]> yeah there is no action to be taken at this time unfortunately other than to wait
[17:45] <dbungert> would we have expected the snapd in impish-proposed to have the libgcc_s fix?
[17:47] <ijohnson[m]> dbungert: the issue is that snapd as a feature will purposefully execute mksquashfs from the snap ignoring whatever version is in the deb world
[17:47] <dbungert> ok, so no change to the deb can conceivably help
[17:49] <dbungert> ijohnson[m]: appreciate the feedback, I think we're good
[17:49] <ijohnson[m]> well we could disable re-exec in the deb so it stops doing that, but it's sort of a feature, so we would want to disable it in a very specific manner, like basically "try re-exec, it if fails specifically because of segfaulting, then use mksquashfs from the host", but that would take time that we don't have a lot of at the moment unfortunately
[17:50] <dbungert> fair
[20:19] <flotter> x86_64 (native)
[20:19] <flotter> ~/snapd$ CGO_ENABLED=1 GOOS=linux GOARCH=amd64 go build -a -o /tmp/build/amd64 ./...
[20:19] <flotter> ARMv8_64 (crosscompile)
[20:19] <flotter> ~/libseccomp$ ./configure --host=aarch64-linux-gnu --prefix=/home/flotter/libseccomp/root
[20:19] <flotter> ~/libseccomp$ make && make install
[20:19] <flotter> ~/snapd$ CC=aarch64-linux-gnu-gcc CGO_ENABLED=1 CGO_LDFLAGS="-L/home/flotter/libseccomp/root/lib" GOOS=linux GOARCH=arm64 go build -a -o /tmp/build/arm64 ./...
[20:19] <flotter> ARMv7 (crosscompile)
[20:19] <flotter> ~/libseccomp$ ./configure --host=arm-linux-gnueabihf --prefix=/home/flotter/libseccomp/root
[20:19] <flotter> ~/libseccomp$ make && make install
[20:19] <flotter> ~/snapd$ CC=arm-linux-gnueabihf-gcc CGO_ENABLED=1 CGO_LDFLAGS="-L/home/flotter/libseccomp/root/lib" GOOS=linux GOARCH=arm go build -a -o /tmp/build/arm ./...
[20:20] <flotter> I have been able to now build snapd on amd64 / arm and arm64. The only dependency was libseccomp, which I cross-compiled for the to non-native builds.
[20:21] <flotter> Is there anything I have done wrong here (conceptionally) ? I verified the ELF files and the headers match the target arch.
[20:22] <flotter> I am asking in the context of trying to update HACKING.md with steps that could help others.
[20:49] <ijohnson[m]> flotter: did you have any problems? I don't see anything conceptually wrong there but the best test would be to see if it just works
[21:35] <mup> PR snapd#10898 opened: cmd/snap-confine/snap-confine.apparmor.in: update ld rule for s390x impish <⚠ Critical> <Simple 😃> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/10898>


[03:20] <elky> AlanBell, see bzr for some ie6 and dots-behind-words fixes.
[03:31] <elky> when it decides to push, that is...
[03:31]  * elky drums fingers.
[03:37] <nigelb> Die ie6 die!
[09:35] <AlanBell> elky: thanks, I will incorporate those at some point
[09:36] <AlanBell> I think one of the next steps is to find out if we are going to be allowed to deploy a new theme to the wiki
[09:36] <AlanBell> or rather what the process and timescale is for doing so, I am sure it will be allowed, but might take forever
[12:55] <elky> That depends who I go pout at if I get to UDS I guess.
[13:03] <AlanBell> you will have to start practicing your best pout
[13:04] <AlanBell> I think you were eating apricots last time you were pouting :-)
[13:35] <nigelb> elky: Just as much as time it takes for pleia2 to do it :)
[13:35] <nigelb> She's got access to the box its running on I believe.
[13:35] <elky> nigelb, not the wiki I don't think
[13:35] <elky> just the site.
[13:36] <nigelb> elky: gah, then I'd encourage you to practice :D
[14:40] <elky> AlanBell, since your rendition of the wiki isn't working i'm guessing your laptop is with you. care to email me (or even commit) the data?
[14:40] <nigelb> heh
[14:40] <AlanBell> oh, I just shut it down!
[14:40]  * nigelb lols some more :)
[14:40] <AlanBell> i think it was fully committed
[14:41] <elky> the actual data?
[14:41] <elky> as in the footer/header files?
[14:41] <AlanBell> ah, they are not data, they are content
[14:41] <elky> :P
[14:41] <AlanBell> one sec . . .
[14:43] <elky> i've got everything else working, i'm just too lazy to go through figuring that stuff out when it's already been done
[14:43] <AlanBell> ok, tiz working
[14:43] <AlanBell> http://libertus.co.uk:88/uw/Header?action=edit&editor=text
[14:43] <AlanBell> http://libertus.co.uk:88/uw/Footer?action=edit&editor=text
[14:44] <AlanBell> ||<tableclass="footer"> is what the stylesheet is looking for
[14:44] <elky> Both open to raw, ta
[14:45] <AlanBell> and the ---------- is important too, it keeps the footer below both the content and the right bar
[14:45] <elky> good old css clear:both wasn't working?
[14:46] <AlanBell> no, because it had to be absolute positioned to get it to the far left outside the container
[14:46] <elky> ah
[14:46] <AlanBell> so it is absolute positioned left:0 relative to the <hr class="hr6"> which is clear:both
[14:49] <AlanBell> so all the pages would end up with <<Include(Header)>> at the top and <<Include(Footer)>> at the bottom
[14:50] <AlanBell> all the stuff that should be content is wiki-editable and only theme stuff that really won't change is in the theme
[14:51] <elky> Exactly how it should be :D
[14:51] <AlanBell> ok, got the bits?
[14:52] <elky> yup
[14:52] <elky> thanks
[14:52] <AlanBell> ok, down it goes again
[15:24] <czajkowski> €625 for 100 t-shirts with logos having to be all one colour is not really what I want :( Womens T-shirts cost an more than €0.75 cent extra per T than mens T due to not being ordered as much and costs more to get them in....
[16:18] <AlanBell> elky: back now. So do you have a local moin up and running now?
[17:00] <pleia2> I actually do have a login to the machine where the wiki lives, but I don't have any permission to *do* anything, permissions are very strict and only given when very specific needs arise
[17:01] <pleia2> so we'll need to ask them, and get elky added
[17:02] <pleia2> I think akgraner has a login there too, I know one was offered, but she didn't reply to the ticket itself I was on so I don't know if it was formally set up
[17:08] <nigelb> pleia2: how does login help if you can't do anything? :(
[17:09] <nigelb> i.e. what point in having it given
[17:10] <pleia2> nigelb: the idea was that the next time the wiki gets attacked we'll be able to lock it down, but we found a way around that with ACLs somewhat, so it never progressed server-side
[17:12] <nigelb> pleia2: Ah!
[17:17] <AlanBell> it would be good to create the theme directory and drop the python file in the right place and have bzr+ssh access for elky to the folder with the css and img stuff
[17:18] <AlanBell> then logged in users could set their own theme to the new one without it being the default for a while
[17:18] <AlanBell> when everyone is happy with it, make it the default
[17:54] <pleia2> then point ubuntu-women.org at it?
[17:55] <AlanBell> I would
[18:09] <AlanBell> http://wiki.ubuntu-women.org/Meetings/20100722#Blueprint updates


[04:39] -queuebot:#ubuntu-release- New binary: rust-gtk4 [riscv64] (kinetic-proposed/universe) [0.3.1-1] (no packageset)
[05:00] -queuebot:#ubuntu-release- New binary: rust-secret-service [riscv64] (kinetic-proposed/universe) [2.0.1-1] (no packageset)
[07:27] -queuebot:#ubuntu-release- New binary: rust-phf [ppc64el] (kinetic-proposed/universe) [0.10.1-2] (i386-excludes)
[08:03] -queuebot:#ubuntu-release- New binary: rust-phf [arm64] (kinetic-proposed/universe) [0.10.1-2] (i386-excludes)
[08:11] -queuebot:#ubuntu-release- New binary: rust-phf [armhf] (kinetic-proposed/universe) [0.10.1-2] (i386-excludes)
[08:16] -queuebot:#ubuntu-release- New binary: node-atomico-rollup-plugin-sizes [amd64] (kinetic-proposed/universe) [1.1.4-2] (no packageset)
[08:16] -queuebot:#ubuntu-release- New binary: ros2-colcon-cd [amd64] (kinetic-proposed/universe) [0.1.1-2] (no packageset)
[08:22] -queuebot:#ubuntu-release- New binary: mkdocs-redirects [amd64] (kinetic-proposed/universe) [1.0.4-1] (no packageset)
[08:28] -queuebot:#ubuntu-release- New binary: ros2-colcon-notification [amd64] (kinetic-proposed/universe) [0.2.13+ds-2] (no packageset)
[08:29] -queuebot:#ubuntu-release- New binary: sphinx-reredirects [amd64] (kinetic-proposed/universe) [0.0.0+git20220411-1] (no packageset)
[08:32] -queuebot:#ubuntu-release- New binary: ros2-colcon-devtools [amd64] (kinetic-proposed/universe) [0.2.3-2] (no packageset)
[09:13] -queuebot:#ubuntu-release- New binary: rust-phf [s390x] (kinetic-proposed/universe) [0.10.1-2] (i386-excludes)
[13:37] -queuebot:#ubuntu-release- New binary: node-y-websocket [amd64] (kinetic-proposed/universe) [1.3.18-4] (no packageset)
[13:38] -queuebot:#ubuntu-release- New binary: ros2-colcon-cmake [amd64] (kinetic-proposed/universe) [0.2.26-3] (no packageset)
[13:51] -queuebot:#ubuntu-release- New: accepted node-y-websocket [amd64] (kinetic-proposed) [1.3.18-4]
[13:51] -queuebot:#ubuntu-release- New: accepted ros2-colcon-devtools [amd64] (kinetic-proposed) [0.2.3-2]
[13:51] -queuebot:#ubuntu-release- New: accepted rust-phf [s390x] (kinetic-proposed) [0.10.1-2]
[13:51] -queuebot:#ubuntu-release- New: accepted ros2-colcon-cmake [amd64] (kinetic-proposed) [0.2.26-3]
[13:51] -queuebot:#ubuntu-release- New: accepted ros2-colcon-notification [amd64] (kinetic-proposed) [0.2.13+ds-2]
[13:53] -queuebot:#ubuntu-release- New: accepted mkdocs-redirects [amd64] (kinetic-proposed) [1.0.4-1]
[13:53] -queuebot:#ubuntu-release- New: accepted ros2-colcon-cd [amd64] (kinetic-proposed) [0.1.1-2]
[13:53] -queuebot:#ubuntu-release- New: accepted rust-phf [amd64] (kinetic-proposed) [0.10.1-2]
[13:53] -queuebot:#ubuntu-release- New: accepted rust-phf [armhf] (kinetic-proposed) [0.10.1-2]
[13:53] -queuebot:#ubuntu-release- New: accepted rust-secret-service [riscv64] (kinetic-proposed) [2.0.1-1]
[13:53] -queuebot:#ubuntu-release- New: accepted node-atomico-rollup-plugin-sizes [amd64] (kinetic-proposed) [1.1.4-2]
[13:53] -queuebot:#ubuntu-release- New: accepted rust-phf [arm64] (kinetic-proposed) [0.10.1-2]
[13:53] -queuebot:#ubuntu-release- New: accepted sphinx-reredirects [amd64] (kinetic-proposed) [0.0.0+git20220411-1]
[13:53] -queuebot:#ubuntu-release- New: accepted rust-gtk4 [riscv64] (kinetic-proposed) [0.3.1-1]
[13:53] -queuebot:#ubuntu-release- New: accepted rust-phf [ppc64el] (kinetic-proposed) [0.10.1-2]
[13:54] -queuebot:#ubuntu-release- New: accepted openrct2 [armhf] (kinetic-proposed) [0.4.0+ds-1]
[15:45] -queuebot:#ubuntu-release- Unapproved: gnome-session (jammy-proposed/main) [42.0-1ubuntu2 => 42.0-1ubuntu2.1] (ubuntu-desktop)
[15:49] -queuebot:#ubuntu-release- New binary: rust-phf-macros [ppc64el] (kinetic-proposed/universe) [0.10.0-1] (i386-excludes)
[15:58] -queuebot:#ubuntu-release- New binary: fastdds [ppc64el] (kinetic-proposed/universe) [2.6.0+ds-3] (no packageset)
[16:04] -queuebot:#ubuntu-release- New binary: rust-phf-macros [amd64] (kinetic-proposed/universe) [0.10.0-1] (i386-excludes)
[16:06] -queuebot:#ubuntu-release- New binary: rust-phf-macros [arm64] (kinetic-proposed/universe) [0.10.0-1] (i386-excludes)
[16:07] -queuebot:#ubuntu-release- New binary: rust-phf-macros [armhf] (kinetic-proposed/universe) [0.10.0-1] (i386-excludes)
[16:07] -queuebot:#ubuntu-release- New binary: rust-clap [ppc64el] (kinetic-proposed/universe) [3.1.6-2] (i386-excludes)
[16:09] -queuebot:#ubuntu-release- New binary: fastdds [amd64] (kinetic-proposed/universe) [2.6.0+ds-3] (no packageset)
[16:23] -queuebot:#ubuntu-release- New binary: rust-clap [amd64] (kinetic-proposed/universe) [3.1.6-2] (i386-excludes)
[16:28] -queuebot:#ubuntu-release- New binary: rust-clap [arm64] (kinetic-proposed/universe) [3.1.6-2] (i386-excludes)
[16:28] -queuebot:#ubuntu-release- New binary: rust-clap [armhf] (kinetic-proposed/universe) [3.1.6-2] (i386-excludes)
[16:29] -queuebot:#ubuntu-release- New binary: fastdds [arm64] (kinetic-proposed/universe) [2.6.0+ds-3] (no packageset)
[16:29] -queuebot:#ubuntu-release- New binary: fastdds [armhf] (kinetic-proposed/universe) [2.6.0+ds-3] (no packageset)
[16:50] -queuebot:#ubuntu-release- New binary: ros2-colcon-ros [amd64] (kinetic-proposed/universe) [0.3.23-1] (no packageset)
[17:10] -queuebot:#ubuntu-release- New: accepted fastdds [amd64] (kinetic-proposed) [2.6.0+ds-3]
[17:10] -queuebot:#ubuntu-release- New: accepted fastdds [armhf] (kinetic-proposed) [2.6.0+ds-3]
[17:10] -queuebot:#ubuntu-release- New: accepted ros2-colcon-ros [amd64] (kinetic-proposed) [0.3.23-1]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-clap [arm64] (kinetic-proposed) [3.1.6-2]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-clap [ppc64el] (kinetic-proposed) [3.1.6-2]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [arm64] (kinetic-proposed) [0.10.0-1]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [ppc64el] (kinetic-proposed) [0.10.0-1]
[17:10] -queuebot:#ubuntu-release- New: accepted fastdds [arm64] (kinetic-proposed) [2.6.0+ds-3]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-clap [amd64] (kinetic-proposed) [3.1.6-2]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [amd64] (kinetic-proposed) [0.10.0-1]
[17:10] -queuebot:#ubuntu-release- New: accepted fastdds [ppc64el] (kinetic-proposed) [2.6.0+ds-3]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [armhf] (kinetic-proposed) [0.10.0-1]
[17:10] -queuebot:#ubuntu-release- New: accepted rust-clap [armhf] (kinetic-proposed) [3.1.6-2]
[17:12] -queuebot:#ubuntu-release- New binary: rust-phf-macros [s390x] (kinetic-proposed/universe) [0.10.0-1] (i386-excludes)
[17:13] -queuebot:#ubuntu-release- New: accepted rust-phf-macros [s390x] (kinetic-proposed) [0.10.0-1]
[17:28] -queuebot:#ubuntu-release- New binary: fastdds [s390x] (kinetic-proposed/universe) [2.6.0+ds-3] (no packageset)
[17:36] -queuebot:#ubuntu-release- New: accepted fastdds [s390x] (kinetic-proposed) [2.6.0+ds-3]
[21:33] -queuebot:#ubuntu-release- Unapproved: zenity (jammy-proposed/main) [3.42.0-1 => 3.42.1-0ubuntu1] (desktop-core)
[22:39] -queuebot:#ubuntu-release- New binary: openturns [riscv64] (kinetic-proposed/universe) [1.18-2] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: libpgf [amd64] (kinetic-proposed/universe) [7.21.7+ds-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: node-concordance [amd64] (kinetic-proposed/none) [5.0.4+~cs5.2.1-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: libpgf [ppc64el] (kinetic-proposed/universe) [7.21.7+ds-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: libpgf [s390x] (kinetic-proposed/universe) [7.21.7+ds-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: libpgf [armhf] (kinetic-proposed/universe) [7.21.7+ds-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: libpgf [arm64] (kinetic-proposed/universe) [7.21.7+ds-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: libpgf [riscv64] (kinetic-proposed/universe) [7.21.7+ds-1] (no packageset)


[01:50] -ubottu:#ubuntu-news- ::planet:: Ubuntu Blog: Strengthen your cloud cyber security with Ubuntu Pro and confidential VMs @ https://ubuntu.com//blog/cloud-cyber-security-with-ubuntu-pro-confidential-vms
[08:21] -ubottu:#ubuntu-news- ::portugal:: E253 Galifão D'Água @ https://podcastubuntuportugal.org/e253/
[14:02] -ubottu:#ubuntu-news- ::omg!ubuntu:: Festival is an Open Source Music Player with a Unique UI @ https://www.omgubuntu.co.uk/2023/06/festival-is-an-open-source-music-player-with-a-unique-ui
[23:42] <guiverc> i just read https://discourse.ubuntu.com/t/ubuntu-desktop-team-indaba-july-28-2023/36597  and I'm wondering if we should include.. new format with pre-recorded interview thus questions need to be far earlier than indaba date of 28-july   (summary maybe worthwhile I think)


[18:47] <slangasek> StevenK: dexter's packages have all been orphaned, which means yada-dropping QA uploads are now in order; do you want to do the honors on libnss-db, or shall I?
[19:05] <infinity> slangasek: !!
[19:05] <infinity> slangasek: Pick me!
[19:12] <infinity> slangasek: If you're not planning on adopting it, I will.
[19:12] <slangasek> infinity: oh, go right ahead, I'm not adopting it :)
[19:13] <infinity> I very nearly hijacked it from him years ago.
[19:13] <infinity> So, may as well just do it.


[02:35] <a1fa> just tried budgie in a vm - very impressed with out of the box experience
[02:36] <a1fa> apt purge kubuntu-desktop
[14:39] <a1fa> yollo


[02:51] <rehcla> Md ?
[04:46] <shawarma> Does upstart have a mechanism for forcing fsck on boot? (Like "shutdown -F" used to do)
[04:48] <_ion> I don't see a reason for it not to be possible.
[04:49] <shawarma> No of course not, but is it already there?
[04:49] <shawarma> brb
[04:50] <_ion> Well, the replacement-initscripts aren't ready yet, the fsck job is yet to be implemented AFAIK.
[05:10] <shawarma> Ok.
[05:10] <shawarma> Thanks
[07:24] <int0x0c> Is there presently a mechanism for starting dbus itself under the  replacement-init-scripts
[07:26] <_ion> The files under etc/event.d in the replacement-initscripts repo is really everything there is so far, unless Keybuk has new stuff not pushed to the repo yet.
[07:28] <AlexExtreme> nope, nothing new there
[07:29] <_ion> dbus will probably be one of the easiest ones, though. :-)
[07:29] <AlexExtreme> yep :)


[15:59] <jokerdino> folks, bringing this to your attention - http://askubuntu.com/questions/123018/unity-quicklists-gtk2
[15:59] <jokerdino> now leaving.
[16:00] <jokerdino> or may i'll just lurk here.
[16:04] <jsjgruber-x-p> http://search.yahoo.com/search;_ylt=AvXXhceCUCkHJATKAo8456KbvZx4?p=cruize+ship&toggle=1&cop=mss&ei=UTF-8&fr=yfp-t-701
[16:05] <jsjgruber-x-p> wrong room, I'm sorry.


[17:54] <Unit193> ki7mt: You can look with bzr blame, or the history of the file.
[17:55] <Unit193> (Which would be gsilva)
[17:59] <ki7mt> Unit193, Ok, yes, I forgot about that. We can pass that along. I can't say why it happened either, maybe a brain fart or something.
[18:00] <ki7mt> Unit193, There's allot of activity happening there at the moment, so maybe in a push to get things moving it was an oversight.
[18:05] <Unit193> wxl: Might be handy to add *.txt~ to bzrignore?
[19:55] <wxl> Unit193: hm?


[03:57] <bear38> arighi: Thanks for checking. So, recompiling the kernel it is in this case. Ty
[17:16] <dijuremo> Hi Everyone, I am running 18.04 with kernel 4.15.0-45-generic and since the update, I am unable to log in to the virtual terminals. There seems to be an automatic carriage return being added, so I am unable to enter the password correctly.
[17:16] <dijuremo> Are there any workaround or fixes for this problem?
[17:22]  * apw wonders if this could be the tty EAGAIN issue
[17:28] <apw> dijuremo, on the assumption you have confirmed booting back to the previous kernel fixes the issue; then there is a fix in -46 which might relate and it is worth testing that kernel (which is in -proposed right now)
[17:30] <dijuremo> apw: Yes, going back fixes it. I am not sure which one was the last one that worked.
[17:31] <apw> worth a try of -46
[17:32] <dijuremo> I believe 4.15.0-43-generic was the last good one and both -44 and 45 have the issue.
[17:32] <dijuremo> I just enable the proposed repo and install it, right?
[17:34] <apw> i would only install the kernel, which should be in the canonical-kernel-team 'proposed' PPA
[17:34] <bear38> Reading this conversation got me wondering. Where is the source code for 4.15.0-45 exactly? Or 4.15.0-46? I am able to find the following link, but that is for 45.48, and I have no idea waht that is. Link: https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-45.48~16.04.1
[17:36] <bear38> Also FWIW virtual TTYs are working fine for me in 4.15.0-45 on 16.04 (ctrl + alt + f2). I know you are on 18.04 though.
[17:36] <apw> bear38, there are tags in the ubuntu git repositories for each version exactly
[17:36] <apw> 4.15.0-46 is an abi number, and the full version is alway longer; as the abi numbers are unique in the context
[17:37] <apw> of the conversation it is easier to just use the short version as it is enough to identify the kernel
[17:37] <apw> but it is only a partial version number, and there is a .N on the end at least
[17:40] <bear38> apw: Thanks, so the official name for -45 includes the .48~16.04.1 suffix. I wasn't sure if the .48 meant it was somehow a middle build. Regarding the git repos though, I was able to find this, but am coming up dry: https://kernel.ubuntu.com/git/?q=<IP_ADDRESS>
[17:40] <bear38> I'm not seeing where the kernel version can be selected there.
[17:46] <apw> bear38, that is a top level of the gits repositories, but generally our master trees are elsewhere
[17:47] <apw> bear38, for example the 4.15.0 kernels are bionic kernels and therefore here: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic
[17:49] <bear38> apw: Thanks, I think I see. So these branches must already have the Ubuntu patches applied, right? Using the link I posted above I had to manually apply the patch.
[18:30] <dijuremo> So I just booted an image which had 4.15.0-42 and it worked fine. My machine had 4.15.0-43 and it worked fine. On the machine I imaged with the 4.15.0-42 kernel, I installed the latest -45 and the problem is present. Next step, try the proposed one and will report back.
[18:46] <dijuremo> I can confirmed that 4.15.0-46 from proposed repository fixes the problem.