=== Class7_ is now known as Class7 === ecloud is now known as ecloud_wfh [06:36] good morning [06:48] hum, my gdm GNOME Shell went crazy CPU wise [06:49] can't reproduce it now though [06:50] Morning didrocks [06:50] Good or bad [06:51] good morning desktoppers [06:52] Hi oSoMoN [06:53] hey duflu & oSoMoN [06:53] didrocks, my user session gnome-shell used to do that occasionally. Stayed high for some time before dropping. [06:53] :( [06:55] Maybe it was the old deferred garbage collection. And it hasn't happened since we started using much more frequent collection [07:02] hey duflu, salut didrocks [07:02] popey, is there a way to get rid of borders around small images in posts on discourse.ubuntu.com ? https://discourse.ubuntu.com/t/monday-1st-october-2018/8203/10 looks kind of ugly === pstolowski|afk is now known as pstolowski [07:06] oSoMoN, may try switching between inline and reference syntax?? https://daringfireball.net/projects/markdown/syntax#img [07:07] +be [07:11] didrocks, I wonder in 19.04 if using the Ubuntu purple wallpaper for the login screen might look nice, or terrible [07:12] duflu, nah, I even tried BBCode and HTML tags, I guess the border is a CSS property applied to all small images, regardless of how they are defined [07:13] oSoMoN, including the old style ? [07:13] which is apparently deprecated in HTML 5 [07:18] ah, I didn't try that [07:18] let's see [07:21] duflu: we can't use wallpapers, due to multimonitor handling in gnome-shell/gdm being bad [07:22] duflu, doesn't work either, nor style="border: 0", which I suppose makes sense, the CSS takes precedence over style attribute in HTML [07:26] Morning desktopers [07:27] Hi Wimpress. Can you answer oSoMoN's question about discourse? ^ [07:34] good morning Wimpress [07:41] good morning desktopers [07:42] Morning folks [07:42] salut seb128 [07:42] buon giorno Trevinho [07:42] lut oSoMoN, en forme ? [07:43] duflu, hi, any idea about the problem with Optimus systems upgraded from 17.10 reported on https://community.ubuntu.com/t/cosmic-cuttlefish-18-10-beta-testing/8132/17 ? [07:43] hey Trevinho, how was Lille btw, I forgot to ask yesterday [07:43] lut jibel [07:43] Salut seb128 [07:43] Merci oSoMoN y seb [07:43] hey seb128 [07:43] seb128, peu dormi, mais oui, le contrecoup viendra après le déjeuner… [07:43] morning Trevinho [07:43] lut didrocks [07:43] oSoMoN, siesta! :) [07:43] I wish… [07:43] :( [07:44] good luck, they eventually do their nights one day :p [07:45] andyrock, jamesh - updates please: https://discourse.ubuntu.com/t/monday-1st-october-2018/8203 [07:45] morning [07:45] willcooke: writing it now [07:45] merci jamesh [07:46] I like this new format to report status updates BTW [07:46] Excellent! Me too. I like oSoMoN's icons especially :) [07:48] Also, you can write your reports almost in changelog format. Only the third indent needs to be - and not . [07:48] seb128, can't even blame the baby, I just went to bed late and then I couldn't sleep for some reason [07:48] jibel, I usually assume I know nothing about Optimus but will check that bug again [07:49] oSoMoN, ah ok, those happens too! [07:50] anyone will a Dell E6430? https://bugs.launchpad.net/nouveau/+bug/1683445 The OEM team don't have one [07:50] Ubuntu bug 1683445 in OEM Priority Project "E6430 brightness control not working" [Critical,Confirmed] [07:50] seb128: very nice... Sunny and tasty salamis there 😂. But really liked. Not touristy, and the place we had was really nice. [07:50] great [07:50] willcooke, I've a 6410 but it's intel only so I guess not good enough to test that bug [07:51] willcooke, why did they flag it "oem priority" if they can't even test it? [07:51] seb128, No worries. I'm not sure what we do in this case, the OP (I think) says he hasnt got the hardware, OEM dont have the hardware, so... [07:51] indeed [07:51] (brb, supermarket delivery) [07:51] we do validate that it has no regression I guess [07:52] the fix might not work but if it doesn't make things work [07:52] and it's supposed to work in theory... [07:52] seb128, how would you feel about pushing LO 6.1.2 to cosmic now? (as opposed to SRUing it after release, which might end up being a SRU of 6.1.3, skipping 6.1.2) [07:53] IIRC Bjoern used to play it safe and prepare a SRU for just after the release [07:57] oSoMoN, +1 from me for uploading now, I think Bjoern was over-cautious, especially for non LTS cycles [07:58] ok, I'll prepare and upload today [07:58] great [07:58] ricotz, FYI ^ [07:59] +1 :) [07:59] you also know libreoffice better than me, how is their testing/the stability of their stable serie updateS? [08:01] * Laney nods [08:01] what up Laney [08:04] hey Laney [08:05] seb128, pretty good in my limited experience, stable series updates are really bugfix-only releases [08:06] hey Laney, how are you? [08:06] oSoMoN, good then :) [08:07] jibel, done and done [08:08] duflu, thanks [08:09] popey: hey! do you mind adding jagger to the yaru / communitheme team? He did some good work on icons and the team +1 on his inclusino [08:09] inclusion* [08:14] hi willcooke oSoMoN seb128 [08:15] even if he has some insane proposal sometimes: https://discourse.ubuntu.com/t/call-for-participation-an-ubuntu-default-theme-lead-by-the-community/1545/1798 (IMHO :p) [08:15] had an early night so i'm good today #thuglyf [08:15] sup [08:15] early night ftw! [08:15] (I did the same ;-) [08:20] :) [08:21] * duflu looks forward to not being jet lagged [08:21] #hazylyf [08:22] coldlyf too [08:22] stupid autumn [08:24] :( [08:24] * didrocks isn't completely out of it yet [08:25] of the jetlag between Lyon and Brussel? ;) [08:25] Lyon is so far south that it takes a while to adjust :p [08:25] no, the cold :p [08:25] ah [08:25] :) [08:25] still coughing [08:26] :( [08:26] get better! [08:26] the kid started sneezing this morning, it's that season again. I hope I'm not next on the list :/ [08:27] thx! yeah, good luck :( [08:39] does ubuntu-bug xserver-xorg works for anyone on cosmic? [08:42] jibel: got the password prompt twice, but I'm on the send/don't send dialog [08:42] and it seems the included info are correct [08:42] hm, it hangs forever here [08:44] didrocks, did you accept to attach DM logs? [08:44] jibel: yes, I accepted both [08:45] weird, it's blocked on the execution of pkexec /usr/share/apport/root_info_wrapper /tmp/tmpo_kbx2jf/:script: [08:45] and :script: is empty [08:45] DM logs is the first prompt, correct? [08:45] (I have 2) [08:47] so, first prompt -> yes -> password; second prompt (for nvidia) -> yes -> password [08:48] k, seems to be just me then. i'll search a bit [08:48] thx [08:49] yw [09:39] Suddenly my Cosmic machine wont boot to a greeter [09:40] it wants to be a server but is too shy to tell you [09:40] :) [10:08] Reinstall sorted [10:08] I will do more testing [10:12] jibel: as per https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292 have you been able to reproduce this again? As I can't anymore it seems now while I lost my /var/crash file :-( [10:12] Ubuntu bug 1794292 in plymouth (Ubuntu Cosmic) "plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in ply_renderer_set_handler_for_input_source -> ply_keyboard_stop_watching_for_renderer_input -> ply_keyboard_stop_watching_for_input -> ply_device_manager_deactivate_keyboards -> on_deactivate" [High,Confirmed] [10:13] Trevinho, I haven't tried since last week. Let me start a VM with latest cosmic [10:14] Trevinho, I explained cypher_mox yesterday how to reproduce it but no news since then [10:21] jibel, I'm seeing a segfault in network manager on Cosmic at start up - did you ever see that? [10:23] it restarts and then seems ok [10:23] willcooke, no, I didn't [10:24] different topic, why is colord lookin for MIB files?! [10:37] willcooke: If I had to guess, it would be libsane doing something not quite. [10:38] * willcooke digs in the logs [10:38] didrocks: replied to vulkan review [10:40] jibel: ah, I got it again [10:46] Trevinho, me too [10:47] gnome-initial-setup is broken [10:48] it shows the online account page and skip or next buttons do nothinh [10:48] g [10:48] is it known? [10:49] andyrock, ^ [10:49] jibel: let me check [10:50] jibel: last iso? [10:50] andyrock, fresh installation [10:50] andyrock, yes [10:51] jibel: also got it... [10:52] jibel: i'll take a look [10:52] works here when tested on a vm [10:52] but not from the last iso [10:54] jibel: also found the issue :) [11:01] heh, when I could finally get in to a working session g-i-s worked ok for me. Odd. [11:02] However, I can't get to a log in screen in a normal boot. [11:02] jibel - before I do digging, you think that is known? I boot and just get a flashing cursor [11:02] tty on 2 [11:07] ok, I think that network manager issues was just a thing. It looks ok now [11:10] seb128, do you have your Inspiron to hand? [11:11] Here's what I'm seeing: Installed daily from yesterday - all fine. Boot machine, get to a black screen with a flashing cursor. Got to tty2 look at syslog, all seems OK. Got to tty a mouse pointer appears. Go back to 1 and there is gdm. [11:11] jibel: works fine here [11:11] Without moving ttys, I just stick at the black screen [11:12] jibel: I installed the last iso on a VM [11:12] logout gets back to gdm [11:12] andyrock, g-i-s working fine here too [11:13] * willcooke -> sandwich [11:13] <- sandwich [11:14] jibel: maybe something is preventing the click to go through? [11:14] jibel: otherwise I'm happy to debug the issue if you send me the vm image [11:23] didrocks: did you ping me somewhere? I saw it when on the train this morning, but can't find it now [11:28] network-manager-gnome broke since the update this morning :( [11:28] anyone e noticed this already? :) [11:31] dupondje, ah, I noticed a segfault in n-m [11:31] but might be unrelated. [11:31] How is it broken for you? [11:32] willcooke: dropdown doesn't show wifi networks anymore [11:32] checking [11:32] huh, and this time when I booted my machine I did get to gdm [11:32] and I have VPN connections for example, those show, but if I click on one, it suddenly connected to another wifi network [11:32] seems like something got randomized :D [11:32] oSoMoN: fixed, no borders round images now. how does that look? :) https://community.ubuntu.com/t/monday-1st-october-2018/8203/10?u=popey [11:33] neither it does show that I'm connected to a VPN, while I am (connected via the settings) [11:33] dupondje, drop down not showing wifi networks - in GNOME Shell? [11:33] 'cos I dont think the drop down ever did [11:34] willcooke: gnome-shell / wayland yes :) [11:34] well you can connect to another wifi via the dropdown ... ? [11:35] From the indicator? [11:41] willcooke: ofcourse? like https://i.stack.imgur.com/QVr1V.png [11:41] https://dflinux.frama.io/thebeginnershandbook/img/deb9-wifi-gnome-1.png [11:42] WiFi is gone now here :) in the indicator [11:44] dupondje, can you check the logs and see if network manager crashed? [11:44] I saw a seg fault this morning, but it seems OK now, and the indicator is working as expected [11:45] willcooke: NetworkManager[1826]: corrupted double-linked list [11:45] but it restarted afterwise :) [11:46] seems to be something else. Yesterday it was fine, today its broken. Seems like only network-manager-gnome package could be the cause? [11:47] I need to get my cosmic machine booting to gdm again and then I can look at this a bit more [11:48] bear with me [11:51] dupondje: which version of gnome-shell? [11:52] http://ubuntu.dupondje.be/bug.jpg -> this it how it looks like here :) [11:53] Laney: 3.30.0-1ubuntu2 [11:53] there were some fixes to network status reporting in 3.30.0-3ubuntu1 [11:53] popey, perfect, thanks! [11:55] Laney: still in proposed I guess? [11:55] it'll migrate shortly [11:56] can I propose a branch to only show desktop file from session-shortcut only in Unity? [11:57] seb128, Laney ^^^ [11:59] gnome-shell has its own versinos of those right? [11:59] Laney: confirmed that resolved it! thx [11:59] willcooke: ^ [11:59] Laney: yep, they got an-all-in-one button [12:00] ok with me then [12:00] dupondje: nice [12:03] andyrock, unity only sounds fine to me yes [12:03] kk preparing a debdiff [12:03] willcooke, I do have the inspiron, I'm going to download the daily iso and do test installs on it [12:04] willcooke, that sounds a timing bug from what you describe, might have to do/be a bug in the new gdm which is stopping the greeter when not needed now (to not have another session in memory for nothing) [12:04] Trevinho, you got a fix for that plymouth issue? well done! [12:04] andyrock, I cannot send a VM image [12:05] it's several GB and will take days to upload [12:05] do you get any error on the command line if you start it manually? [12:07] andyrock, actually it seems to be a problem with xorg, the screen is not refreshing completely [12:08] if I minimize/restore the window it's as expected [12:08] jibel: ah, yeah I wrote before that maybe something was preventing the click to go through [12:09] try also to just move the window around [12:12] seb128, yeah switching to tty2 and then back to tty1 brings up gdm [12:13] a debug log would be good (turn it on in /etc/gdm3/custom.conf, reproduce the bug and then grab the journal) [12:13] willcooke, can you maybe enable Debug=true in /etc/gdm3/gdm.conf, reboot, get the issue and open a bug with ubuntu-bug gdm3? [12:13] IW IN [12:13] or what Laney said for the filename :p [12:13] AHAHAHAH [12:13] :) [12:14] dupondje, Laney @ n-m: ack, thanks [12:14] that sounds related to this work in 3.30 though [12:15] if so it'll be one to file upstream as well probably, for halfline to have a look at [12:15] we already fixed a few like that [12:15] * Laney sammich [12:15] willcooke, bonus point if you file the bug with log on gitlab: ) [12:15] * willcooke gives it a go === pstolowski is now known as pstolowski|lunch [12:24] hm, I dont see anything obvious in the logs [12:29] popey: yeah, I was asking if you can add jaggers to the communitheme/yaru team group please [12:36] willcooke, no need for it to be obvious, it should be verbose is the debug=true worked and hopefully include the details upstream needs [12:59] k, updating to proposed seems to have fixed it [12:59] sorry [12:59] I will retest a few times === pstolowski|lunch is now known as pstolowski [13:07] * didrocks is fighting still on gsconnect… [13:08] willcooke: I'm unable to reply to the team report community thread [13:09] I have a concern about the tracker MIR [13:12] tseliot: you could have written that in the description :/ [13:12] tseliot: so basically I've spent the whole morning reviewing the MIR for nothing? [13:13] didrocks: wrong ping? [13:13] tseliot: sorry, was for tjaalton :) [13:13] good :) [13:13] too many t* [13:14] tjaalton: please have a look ^ and you didn't explain why the split (I requested this) and the difference: what would be in vulkan vs vulkan-loaders, what the MIR will use then [13:14] and as long as it's not NEWed, I don't think I'm going to rereview it, as those questions aren't answered :/ [13:15] @didrocks done [13:15] (if I understand correctly, vulkan is going to be an empty package, split in 4 sources, but only -loader would need a MIR) [13:15] popey: thanks! [13:15] would like a confirmation still, quite unclear [13:17] jbicha, the hub topic is not supposed to be for discussion, that's by design [13:17] we discuss topics on IRC during the meeting [13:17] or we said we would have a "discussion" post for comments [13:19] so I should just start a regular desktop topic for the tracker issue? [13:19] or raise it to discuss during the IRC meeting [13:19] as you prefer [13:19] or talk about it here now [13:19] opening a topic since it's easier to read there [13:19] good [13:21] https://community.ubuntu.com/t/tracker-stuck-in-cosmic-proposed/8224 [13:21] didrocks: the split was mentioned in the description [13:21] jbicha, ah. My bad. popey please could you grant jbicha permission to post to the weekly updates topic? [13:21] didrocks: only loader will need the MIR [13:21] we can discuss elsewhere but that gives background easier [13:22] didrocks: upstream did the split, so it had to be repackaged [13:22] tjaalton: right, but you could have said to not review vulkan then [13:23] MIR is already unfun, we were supposed to have 2 people from the desktop team but seems the plan was cancelled, and I'm not really fond of loosing a morning on things like that :/ [13:23] jbicha, caught up with backlog now - so yeah, that list is for weekly updates, which you might still want to post to, so we should still sort that, but as seb said, discussion should be in a new topic and/or the meeting [13:23] tjaalton: so, basically, only -loaders, once NEWed will need a MIR review? [13:23] which is a subpart of vulkan [13:23] correct? [13:23] I didn't prepare an update for this week so unless I type really fast… [13:24] didrocks: correct [13:24] willcooke: done [13:24] thanks popey [13:24] tjaalton: ok, and as you said, the vendoring will not be part of the package anymore [13:24] jbicha, you can add it later if you like [13:24] no way to file it against vulkan-loader before it's in the archive, my mistake for subscribing ubuntu-mir then, it was meant to be a placeholder [13:24] tjaalton: so, I suggest that you look at my comments, and already fix some I had if that applied to the new package [13:25] so that already this is done and we win a loop [13:25] however, we'll need someone to NEW the package first [13:25] I've tried [13:26] (I don't want to cumulate NEWing and MIRing, better having someone else having a look) [13:28] jbicha: the tracker code is very different than the one we used to have in main [13:28] and as I have written, I already have doubt security-wise on file permissions [13:28] I don't think telling "double guessing what the MIR team applied and bypass security" is a good option [13:29] it's too late in the cycle to promote/add to default install anyway [13:29] It's meeting time [13:29] Do you want a few mins to wrap that up? ^ [13:30] Or we can do it in the meetnig [13:31] I guess in meeting if needed is good [13:31] Laney, seb128, just before we start - now running proposed at I've got gdm up 4 times out of 4 so far [13:31] going for #5 now [13:31] ok, goingt to start then [13:31] #startmeeting Desktop Team Weekly Meeting - 2018-10-02 [13:32] Meeting started Tue Oct 2 13:31:59 2018 UTC. The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [13:32] Available commands: action commands idea info link nick === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: [13:32] :) [13:32] Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot [13:32] hey [13:32] o/ [13:32] o/ [13:32] \o [13:32] o/ [13:32] o/ [13:32] o/ [13:32] New format this week then everyone. You should have had a chance to review people's updates. I've had no messages for anyone in far away places that they want to raise any topics. [13:33] o/ [13:33] o/ [13:33] #topic Round table === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: Round table [13:33] By a show of hands, does anyone have anything they want to raise based on the updates from the rest of the team, or otherwise? [13:33] i.e. if no one wants to talk about anything, then we can move on to rls bugs [13:33] o/ [13:34] just that I'm fighting with gsconnect extension [13:34] upstream is really responsive [13:34] I hope to upload a new snapshot soon [13:34] tjaalton, is that "I want to talk about something" or just a "I'm here!"? [13:34] it will still be in universe, but if people want to give a test [13:34] didrocks, that's great to hear, thanks! [13:34] willcooke: I'm here :) [13:34] the idea is that the code will be close to what we want to ship by default next cycle [13:34] better [13:35] so, the earlier you test with your phone, the better :) [13:35] just for next time, maybe standardize on a round of "o/ I've a topic" [13:35] that's it for me [13:35] then we can go round between those who said that [13:35] with the chair giving the turn to each [13:35] otherwise it's going to be cahos [13:35] that's what I was going for here [13:35] seb128: +1 [13:35] willcooke, right [13:35] NM's definitely being crashy here too, took me a while to get online after rebooting just then [13:35] but tjaalton did an unclear o/ [13:35] and didrocks just wrote [13:36] yeah, better to standardize [13:36] o/ [13:36] lol [13:36] see jbicha also :p [13:36] I have a question as well [13:36] ok, let's start with jbicha [13:36] #topic jbicha === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: jbicha [13:36] was that a raise of hand or an "hey"? [13:36] I had a tracker question but it was late so maybe discuss that on the community site? [13:37] we can discuss it now [13:37] imho [13:37] ok: https://community.ubuntu.com/t/tracker-stuck-in-cosmic-proposed/8224 [13:37] can we fast track the tracker mir? [13:38] no [13:38] didn't we just discuss how bad the idea of fast tracking the tracker mir ? [13:38] gotta track the tracker [13:38] security team has some backlog, we have no impact on that, and in fact we are more import MIRs we want to get through (portals) [13:38] didrocks: sorry, I might have missed that discussion [13:38] and it's not a good idea to add a feature that late [13:39] on the MIRing side, this is my view: [13:39] jbicha: the tracker code is very different than the one we used to have in main [13:39] and as I have written, I already have doubt security-wise on file permissions [13:39] ok, maybe I'll talk to mbiebl about letting the package split in [13:39] I don't think telling "double guessing what the MIR team applied and bypass security" is a good option [13:39] would need a ffe at least [13:39] I would be fine deleting the new tracker from cosmic-proposed [13:39] it didn't migrate out and we don't need that update [13:39] but if you have an easy fix that works too [13:40] it's getting a bit late to land a new version now (having it not migrated out of proposed yet means it virtually haven't landed/got testing) [13:40] let's see if the split works, otherwise I'm fine with dropping it from -proposed [13:40] wfm [13:40] /next topic [13:40] cool, thanks. We know where we're going then [13:40] #topic willcooke === meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting - 2018-10-02 | Current topic: willcooke [13:41] tjaalton, I'm keen to hear if you're any closer to understanding why virtualbox machines won't start without nomodeset [13:41] That's a release blocker for me [13:42] willcooke: the kernel driver init takes 25-30s on initial boot, probably because the driver is not in the installer initrd [13:42] this triggers a weird race in xserver which has been there for some time already [13:42] "probably because the driver is not in the installer initrd" [13:43] how can we get that "probably" out of the sentence? [13:43] has the vbox driver already been in the installer initrd? [13:43] that [13:43] and if it was, when/why has it been removed? [13:43] seb128: is not according to lsinitrd [13:43] and if it was not why is it failing now? [13:43] lsinitramfs [13:44] maybe we're faster in doing something else and thus.... [13:44] the issue. === Class7_ is now known as Class7 [13:44] like we try to start x when things are not ready yet, while before this was delayed by something else. This sometimes happen. [13:44] $ lsinitramfs /boot/initrd.img-4.4.0-116-generic | grep virtual [13:44] lib/modules/4.4.0-116-generic/kernel/drivers/regulator/virtual.ko [13:44] on xenial [13:45] so it was in the initramfs [13:45] as per listing initrd there's no x11 related video drivers there [13:45] or is that a different one? [13:45] lib/modules/4.18.0-8-generic/kernel/drivers/regulator/virtual.ko [13:45] it's still in the initramfs [13:45] seb128: vboxvideo [13:45] didrocks, wrong name, sorry :p [13:45] tjaalton, that was not in xenial either [13:45] this one is not, was it in xenial? [13:45] ok [13:45] yeah, no video driver is there iirc [13:45] is it possible to add it and test if it works? [13:46]