didrocks | good morning | 06:28 |
---|---|---|
duflu | Morning didrocks | 06:42 |
didrocks | hey duflu! | 06:45 |
duflu | It's a new day... | 06:46 |
didrocks | heh, a new area :) | 06:48 |
c-lobrano | good morning! Congratulation for the new LTS ;) | 06:53 |
=== pstolowski|afk is now known as pstolowski | ||
jibel | Good morning | 08:04 |
didrocks | salut jibel, ça va ? | 08:06 |
jibel | salut didrocks, ça va bien. Après une journée pleine de rebondissements, la release a enfin vu le jour donc tout va bien :) | 08:06 |
didrocks | jibel: ouais, c'était assez épique :) | 08:07 |
didrocks | jibel: si on avait utilisé mon workaround safe de mardi plutôt que "the right thing", ce side effect n'aurait pas eu lieu :/ | 08:07 |
jibel | l'essentiel c'est d'avoir release on-time une fois de plus meme si c'était un peu mouvementé | 08:11 |
didrocks | yep ;) | 08:11 |
jibel | looking at incoming bug reports the main problem with the installer is the removal of the big fat warning when doing an efi install with an existing legacy system installed | 08:12 |
jibel | grub crashes | 08:12 |
didrocks | argh | 08:12 |
jibel | and regarding upgrades there is this nasty "triggers looping" bug | 08:13 |
pitti | bonojur tout le monde ! | 08:15 |
pitti | congratulations to 18.04 LTS! | 08:15 |
didrocks | yeah, the triggers looping one :/ | 08:15 |
didrocks | Guten Morgen pitti! Danke Schon | 08:16 |
pitti | so, gnome-shell LTS :) | 08:16 |
didrocks | yes! We'll see how that goes :) | 08:17 |
duflu | Morning jibel, pitti | 08:18 |
jibel | Bonjour pitti and duflu | 08:21 |
seb128 | good morning desktopers | 08:27 |
seb128 | congrats on the release everyone! | 08:29 |
didrocks | salut seb128 :) Congrats as well ! | 08:29 |
jibel | Salut seb128 | 08:30 |
duflu | Morning seb128 | 08:31 |
duflu | Odd the number of 16.04 and 17.10 bug reports I've seen today | 08:31 |
willcooke | morning all | 08:32 |
duflu | Morning willcooke | 08:32 |
didrocks | hey willcooke | 08:32 |
seb128 | hey willcooke | 08:32 |
willcooke | reports from OEM seem to show that bolt is working as it should | 08:33 |
didrocks | nice | 08:33 |
duflu | Is that something holding up the metaphorical structure, or Thunderbolt? :) | 08:34 |
willcooke | they're getting the notifications when the plug a thunderbolt device in | 08:35 |
seb128 | and the prompt seems to success to auth the device so it can be used | 08:38 |
willcooke | \o/ | 08:40 |
zyga | hey | 08:43 |
zyga | does bionic have gnome shell <-> bolt thunderbolt integration? | 08:43 |
zyga | oh | 08:43 |
didrocks | hey zyga! see the discussion we just got :) | 08:43 |
zyga | I see thunderbolt is being discussed :D | 08:43 |
zyga | man so funny | 08:43 |
didrocks | heh | 08:43 |
tjaalton | huh, win+arrow changed the tty, not the window location | 08:43 |
tjaalton | wth | 08:43 |
zyga | do we plan to back port bolt 0.3 to bionic? | 08:44 |
seb128 | what do you need from it? | 08:45 |
seb128 | upstream said there was nothing "important" and that we were fine staying on 0.2 | 08:45 |
zyga | I don't know yet, just parity I would say | 08:45 |
seb128 | parity with? | 08:45 |
zyga | but if it's just internal refactoring then perhaps not worth it | 08:45 |
zyga | with F28 | 08:45 |
seb128 | what's the interest? | 08:46 |
zyga | though it would be nice to have LTS-ish release | 08:46 |
seb128 | newest isn't always better or more stable | 08:46 |
seb128 | that component is really young | 08:46 |
zyga | that true but I don't know if 0.2 will be maintained over time | 08:46 |
seb128 | I expect quite some changes | 08:46 |
zyga | so probably saying on the moving version is better | 08:46 |
zyga | but maybe not, just curious | 08:46 |
seb128 | you seem interested | 08:46 |
zyga | now that I have a thunderbolt port :) | 08:46 |
seb128 | want to become the maintainer in Ubuntu? | 08:47 |
seb128 | :) | 08:47 |
zyga | I don't know what kind of work that is coupled with TBH | 08:47 |
zyga | I can help with testing for sure, I have some hardware and I'm genuinely interested in the technology | 08:47 |
willcooke | its a trap | 08:47 |
seb128 | willcooke, shush :p | 08:49 |
zyga | oh noes, the death start is operational ;D | 08:49 |
seb128 | zyga, joke aside, 0.3 was just too close from release and I talked to upstream and he said there was no strong reason that we needed to update | 08:50 |
zyga | seb128: understood, thank you :) | 08:50 |
seb128 | but that component is new and changing | 08:50 |
seb128 | and it's hardware enablement | 08:50 |
willcooke | we will be adding new a new settings panel to B though | 08:50 |
seb128 | so I expect we are going to SRU new versions | 08:50 |
willcooke | for TB | 08:50 |
seb128 | and add the control panel for LTS .1 | 08:50 |
jbicha | zyga: want to become the maintainer in Debian? ;) | 08:50 |
jbicha | good morning | 08:50 |
zyga | jbicha: good morning | 08:50 |
zyga | jbicha: I suppose I can co maintain it there, sure | 08:51 |
seb128 | trolling doesn't work on him :p | 08:52 |
seb128 | even on a friday! | 08:52 |
zyga | I'm really interested | 08:52 |
willcooke | morning jbicha | 08:52 |
jbicha | zyga: I guess https://salsa.debian.org/freedesktop-team/ would be a good place for it | 08:53 |
seb128 | zyga, anyway we welcome testing & feedback in any case | 08:54 |
seb128 | so let us know if/how it works for you | 08:54 |
zyga | I'm trying right now | 08:54 |
zyga | is bolt responsible for anything thunderbolt or just certain kinds of devices | 08:55 |
zyga | for instance TB3/USB adapter seems to be transparent, probably just using usb mode of usb-c | 08:55 |
zyga | I need to try with an ethernet adapter next | 08:55 |
jbicha | zyga: we appreciate the testing. I don't think any Desktop team members have thunderbolt devices yet | 08:57 |
zyga | jbicha: I wonder if it depends on apple vs non-apple | 08:57 |
zyga | I have a thinkpad with a single TB3/usb-c port | 08:57 |
zyga | I just purchased some adapters, I will have them next wee | 08:58 |
zyga | week | 08:58 |
willcooke | zyga, are you in Berlin next week at the product sprint? | 09:01 |
zyga | no, sadly not | 09:01 |
zyga | I could drive over if you need me to :) | 09:01 |
zyga | (well, on the train) | 09:01 |
zyga | mvo will be there | 09:01 |
zyga | why do you ask? could I help somehow? | 09:02 |
willcooke | zyga, nah s'fine - was looking to play with some TB hardware :) | 09:02 |
zyga | I had it the last time in Budapest :) | 09:08 |
willcooke | we didnt have bolt MIRed at that point | 09:08 |
willcooke | I think | 09:08 |
zyga | ah I see | 09:08 |
zyga | I didn't know about it before I read F28 release news | 09:09 |
andyrock | good morning! | 09:11 |
willcooke | hey andyrock | 09:15 |
seb128 | hey andyrock, how are you? | 09:18 |
andyrock | hey seb128! fine you? | 09:19 |
seb128 | I'm good thanks | 09:19 |
andyrock | checking errors.ubuntu.com | 09:19 |
andyrock | :D | 09:19 |
seb128 | enjoy my day off by chatting with nice desktop people about the new Ubuntu :) | 09:19 |
seb128 | haha | 09:19 |
didrocks | andyrock: you can see how seb is totally off ;) | 09:20 |
andyrock | lol | 09:20 |
duflu | andyrock, I think it's too early to check the error stats. It takes a week or two for most people to upgrade | 09:25 |
jbicha | in other news, Fedora 28 will release in a few days, on time for once: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UDWYTL2WYIU7P6UPQUGWNNQQZ3WLZ6HL/ | 09:25 |
duflu | Also morning andyrock | 09:25 |
willcooke | is that xorg issue someting we should flag up right away? | 09:26 |
duflu | willcooke, which issue? | 09:35 |
willcooke | oh, ignore | 09:36 |
willcooke | :) | 09:36 |
willcooke | hm | 09:36 |
willcooke | https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 | 09:36 |
didrocks | zyga: hey, does is make sense for my classic snap to try using ld-linux from the core snap? | 09:37 |
didrocks | zyga: lead myself to a segfault | 09:37 |
zyga | yes, it should | 09:38 |
didrocks | zyga: I think there is a bionic vs xenial issue though… | 09:38 |
didrocks | Program received signal SIGSEGV, Segmentation fault. | 09:38 |
didrocks | 0x00007ffff7dda949 in ?? () from /snap/core/current/lib64/ld-linux-x86-64.so.2 | 09:38 |
didrocks | in gdb | 09:38 |
didrocks | for a go program | 09:38 |
duflu | willcooke, yeah I was thinking about that bug again recently, as it happens. | 09:42 |
duflu | I've been frustrated at how non-obvious and hard it is to just launch 'Xorg' | 09:43 |
duflu | Turns out you need to tell it the current VT: Xorg :0 vt4 | 09:43 |
duflu | Happy release weekend peoples | 10:10 |
* duflu shuts down | 10:10 | |
didrocks | see you duflu! | 10:11 |
willcooke | brb | 10:22 |
=== jhernandez is now known as jhernandez_ | ||
Laney | moin | 10:59 |
=== JanC is now known as Guest28882 | ||
=== JanC_ is now known as JanC | ||
=== sergiusens_ is now known as sergiusens | ||
ads20000 | willcooke: the link to the communitheme snap in your bionic insights article is wrong | 11:58 |
ads20000 | it points to https://communitheme rather than snap://communitheme :) | 11:58 |
Laney | EPIC FAIL | 13:19 |
willcooke | stupid wordpress | 13:20 |
marathone | Congratulations to the Desktop Team! | 13:25 |
acheronuk | hi. is intended to still have "update-manager -cd" and "sudo do-release-upgrade -d" in the release notes? | 13:31 |
marathone | !isitout | 13:34 |
ubot5 | Yes, it's out! Party in #ubuntu-release-party :) | 13:34 |
willcooke | acheronuk, ah, good spot. Thanks | 13:37 |
acheronuk | np | 13:37 |
* willcooke heads home | 13:38 | |
willcooke | "see" you next week on IRC | 13:38 |
acheronuk | hmmmm. willcooke's edit lock on the releasenotes wiki page expired. maybe went home without making any change? | 13:58 |
acheronuk | I would just remove the -d if that is what you want, but not sure if it's intended to put some explanation in it's place that upgrades are not turned on in the meta just yet? | 13:59 |
jbicha | acheronuk: the -d is still needed until http://changelogs.ubuntu.com/meta-release is updated | 14:01 |
acheronuk | jbicha: that was why I asked if it was intentional. i.e. that you wanted the instructions in the main notes to force upgrades now, even though the meta is not updated | 14:03 |
acheronuk | so all is good if that is what you want :) | 14:05 |
jbicha | acheronuk: unless you want to add an explanation of why the "-d" is needed for the next few days… | 14:06 |
mgedmin | that would be very welcome; I _always_ get confused the first day after a release, before the meta-release gets updated | 14:08 |
jbicha | mgedmin: do you have wiki write access? I guess a note would be good since all of these third party sites will post instructions using " -d" and that will be Fun when we open up Chaotic Chameleon for updates | 14:58 |
mgedmin | I doubt I have access | 14:59 |
* mgedmin is currently recovering from a failed 17.10 -> 18.04 upgrade | 14:59 | |
Laney | umm, no, we should just be advising people to wait until it's turned on | 15:00 |
jbicha | ok, let me do that… | 15:00 |
Laney | the reason there's a little delay is to give a chance to shake out upgrade bugs if there are any | 15:01 |
Laney | thx! | 15:05 |
mpt | didrocks, jbicha: How do I re-run gnome-initial-setup if it’s already run? (Typing “gnome-initial-setup” at the terminal claims it’s not found, but trying to install it says it’s already manually installed.) | 15:43 |
jbicha | 2 ways: | 15:49 |
jbicha | /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-user | 15:49 |
didrocks | mpt: you need to run /usr/lib/gnome-initial-setup/gnome-initial-setup --existing-use, but it have a missing lib that way | 15:49 |
jbicha | or just rm ~/.config/gnome-initial-setup-done | 15:49 |
didrocks | ah no, it should be fine in your system | 15:49 |
didrocks | mpt: if you remove the file jbicha points at, you need to logout/login again | 15:49 |
jbicha | didrocks: no you don't :) | 15:50 |
didrocks | hum | 15:50 |
didrocks | you mean i just have to remove the file and the autostart will kick in? | 15:50 |
jbicha | yes :| | 15:50 |
mpt | Ask two people, get three answers :-D | 15:50 |
didrocks | waow, didn't know the check was done regularly in Application phase | 15:50 |
didrocks | mpt: because we love you :) | 15:51 |
jbicha | you have to log out for the first time if gnome-initial-setup wasn't installed before, see LP: #1697769 for the similar tracker issue | 15:51 |
ubot5 | Launchpad bug 1697769 in tracker (Ubuntu) "tracker doesn't automatically start when installed until after log out and log in" [Medium,Confirmed] https://launchpad.net/bugs/1697769 | 15:51 |
mpt | Hmm, so the window is not closable, minimizable, or unmaximizable, but you can drag it away from the top bar, which makes it 242*56 pixels. That’s interesting behavior. | 15:52 |
jbicha | if you have a big enough screen, it's not maximized | 15:56 |
jbicha | but in that case, it's not movable either! | 15:56 |
didrocks | have a good week-end everyone! | 16:05 |
fuzzylaw | Hey guys, How do I enable workspace isolation in ubuntu 18.04? | 16:33 |
=== pstolowski is now known as pstolowski|eow |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!