[01:07] how does one search the mailing list [01:07] all I can find are these crappy archive pages [01:07] which doesn't really do much for me [01:07] you could do a google site search [01:08] true [01:08] there isn't an interface to search through the mailing lists on the ubuntu site? [01:14] seme: Which mailing list? [01:15] ubuntu-devel-discuss [01:15] seme: http://dir.gmane.org/index.php?prefix=gmane.linux.ubuntu Archives a lot of them, and has some more searchability http://dir.gmane.org/gmane.linux.ubuntu.devel.discuss [02:06] in ubuntu bugs advanced search, would it be useful to have an option to show bugs that have been reproduced? i think it would help devs. [02:07] since there is already a flag for it in launchpad i don't think it would be too difficult to add. [02:09] fcuk112: in theory, all bugs in Triaged state, and a lot of the Confirmed have been reproduced, or considered good enough for maintainer attention [02:15] hggdh: hummm it is not always the case... a count of how many people are impacted would be useful too to allow devs to focus their energy. at the moment it's hard to seperate those nasty transient bugs from those that can easily be reproduced and resolved. another thing i have an issue with it is hard to drill down into bugs that don't yet have a patch. [02:16] well. For the count -- the "I am/am not affected" helps there, as does the # of duplicates [02:17] for the "without a patch" -- a bit more difficult, since most of the times we end up upstreaming the issue [02:17] but, anyway [02:17] we already have quite a number of bugs *with* patches, and still have not gone through them [02:18] so I am not sure how much it would help, having this option [02:19] finally -- if a triaged bug is not good enough for maintainer's attention... then it probably means it has been raised to triaged erroneously [02:22] Yes, the "I am/am not affected" is useful, it would be nice to have an additional column in the search results screen to show # affected. What do you think? [02:24] now, yes, I agree. it should be visible, either in the search, or in the bug itself [02:26] can we get someone to look into it? what would be the best way to do that? [02:26] fcuk112: there should already be a bug report for it [02:26] * micahg is looking [02:26] this would be a Malone (the LP bug tracker component); I would be surprised if there is not already a but for it [02:26] heh. micahg preempted my response [02:27] :) [02:27] bug 271332 [02:27] thanks micahg [02:28] ugh, any estimate on ubot4? [02:28] https://bugs.edge.launchpad.net/malone/+bug/271332 [02:28] not to my knowledge. jdps was/is looking [02:30] just subsribed myself to the bug. "the next few days", it says. since what, May? [02:30] it's low priority with no one assigned, doubt it'll be looked at before mid next year [02:30] nooo, since Sep 2008! [02:30] it's open source though, so they take patches :) [02:31] I guess so. Pretty good point for a hacker to look at [02:31] dammit. Again you preempted me ;-) [02:51] hi [02:51] I recently downloaded the Ubuntu Karmic Koala and installed it on my Samsung NC10 netbook. [02:52] I am getting a mountall error while booting up Ubuntu on this netbook [02:52] Please help [02:52] linuxuser_ubuntu: try #ubuntu [02:53] micahg, this is posted as a bug in launchpad https://bugs.launchpad.net/ubuntu/karmic/+source/mountall/+bug/456806 [02:54] linuxuser_ubuntu: ok, so you're asking about the bug...we don [02:54] micahg, which is why I posted this in this channel [02:54] ''t do regular support, but we do look at and help file bugs :) [02:54] * micahg is looking [02:54] micahg, the bug is cosidered to be fixed but I do not see a solution listed there [02:54] linuxuser_ubuntu: it's been fixed in the latest development version [02:55] linuxuser_ubuntu: you said it happens when you boot though [02:55] micahg, yes it happens when linux is loading [02:56] linuxuser_ubuntu: does this work for you? https://bugs.edge.launchpad.net/ubuntu/karmic/+source/mountall/+bug/456806/comments/8 [02:56] also, a new mountall has been released (probably in karmic-proposed now [02:57] micahg, the exact error I get is mountall: fsck . [607] killed by TERM signal.General fsck error [02:57] hggdh: nothing in proposed yet [02:57] oh [02:57] Scott released on Lucid [02:57] yep [02:57] so we need a SRU [02:58] hggdh: that's why I was asking linuxuser_ubuntu if that fix in the comment works :) [02:58] but yes, comment 8 should do the trick [02:58] hggdh: that's the one I posted [02:58] micahg, I will check it out and see if it works for me. [02:58] yes indeed, I was acknowledging you [02:58] linuxuser_ubuntu: if you confirm it does, I'll prepare the patch [02:59] SRUitis still strorn, I see ;-) [02:59] strong [02:59] hggdh: just uploaded a test build for apparmor allowing chromium :) [02:59] LOL [03:00] I see my SRU for apport still didn't wasn't allowed :( [03:01] or rather approved [03:02] I think they are busy with alpha1 right now [03:02] yeah [03:03] micahg, Thanks a lot. I think it has solved my problem. [03:04] ok, I'll prepare the patch a little later [03:04] thanks linuxuser_ubuntu [03:04] linuxuser_ubuntu: can you add a comment on the bug stating you tested it and it works? [03:05] hggdh, Yes I will. How do I do it ? [03:05] hggdh: actually, it might be better if linuxuser_ubuntu tests a build I make with the patch [03:05] ah, OK. linuxuser_ubuntu ^^ [03:06] micahg, I may not be able to download the patch if it is huge. I am using a 64kpbs dialup connection. heh [03:06] and, with that, I call it a night. Bed awaits [03:06] \quit [03:34] * bcurtiswx kicks micahg's ethernet card [03:34] bcurtiswx: ath9k on karmic :) [03:34] :) [03:34] * micahg probably needs a reboot after the kernel update [03:35] * bcurtiswx knows you will [03:35] * micahg didn't think it would kill the wireless [03:47] bcurtiswx: just rebooted so I hope it's better :) [03:48] micahg: yeah hopefully [04:04] hi [04:04] when is the gcc version going to be updated from gcc version 4.4.1 to 4.4.3 ? [04:07] spO: lucid is on 4.4.2 right now [04:07] yeah [04:07] well when is karmic going to use 4.4.2 ? [04:07] karmic will not be changing [04:07] are karmic people sleepy or something? how do i update that and allow everyone else to updat eit [04:07] huh? [04:07] WTF [04:08] spO: we don't jump versions in stable releases [04:08] is this because karmic was a mishap? [04:08] i heard that karmic was a mishap [04:08] spO: what do you mean? [04:08] 4.4.0 and 4.4.1 are said to be HIGHLY BUGGY [04:08] [19:43:59] * Now talking in #mplayer [04:08] [19:43:59] * Topic is 'Do NOT paste inside the channel, use www.pastebin.com | gcc 4.4.0 causes problems, use >= gcc 4.4.2 | http://wiki.multimedia.cx/index.php?title=MPlayer_FAQ | svn co svn://svn.mplayerhq.hu/mplayer/trunk | 64bit real codecs available, win32 dlls still need 32bit mplayer, in /usr/local/lib/codecs | 1080 h264 requires 2.4ghz c2d / amd x2 2.8ghz+ | no plugin help | windows builds: http://oss.netfarm.it/mplayer-wi [04:09] the gcc version is not stable [04:09] spO: the karmic version has been patched quite a bit [04:09] ? [04:09] spO: is something still broke? [04:09] just rad that topci okay [04:10] spO: I donm't see anything there [04:10] i don't like you [04:10] !coc > sp0 [04:11] ubot4: I need you [04:11] Factoid 'I need you' not found [04:11] ubot4: coc [04:11] The Ubuntu Code of Conduct to which we ask all Ubuntu users to adhere can be found at http://www.ubuntu.com/community/conduct/ [04:11] ? [04:11] are you joking? [04:11] spO: no [04:12] whatever you think I did, you lacked respect for what i said [04:12] this is highly subjective [04:12] You said you don't like me, that violates the coc as I understand it [04:12] * micahg is trying to help [04:12] i kept on saying something, and you acted like you didn't understand what iw as saying [04:13] it was meant to cause disrespect for the words that i said [04:13] you said gcc-4.4 was buggy before 4.4.2, you posted a link with no information, I asked you for another one [04:13] the #mplayer topic says that 4.4.0 and 4.4.1 cause bugs [04:13] you can go to #mplayer [04:13] they are the people who wrote it [04:14] spO: I don't have time to chase a ghost...do you have a link to gcc or something more authoritative? [04:15] you cause me frustration and stress [04:15] spO: you might want to take this to #ubuntu-devel [04:27] ubuntu-bug xserver-xorg-video-nouveau = "Collecting problem information ... This might take a few minutes. ............." it just filled the 80x25 screen with 2000 dots, at about 1/2 sec per is 15 minutes. I have never seen it take this long. [04:28] any chance it is stuck in a loop? [04:34] I went to report a bug and i was redirected to this page -- https://help.ubuntu.com/community/ReportingBugs [04:35] At the beginning of that page it says, If you've come here when trying to file a bug about Ubuntu in Launchpad this was deliberate. [04:35] Does that mean that it's some sort of punative action? [04:36] no [04:36] Something about it seems wrong. And the wording makes it seem like I was kicked from launchpad. [04:36] yeah, I was kind bothered by it too [04:36] the entire experience makes me feel like saying fine then forget it. It's already a bit of a hassle to bother reporting a bug. [04:37] ditto [04:38] especially when the recommended "utunbu-bug" thing as been collecting info for over 20 min... grumble [04:39] I am sure the number of reports has dropped. I only hope that the quality of info has made up for it [04:41] CarlFK: the number hasn't dropped and the quality is better [04:41] Bleh, why did they have to add *that* crap to Launchpad? [04:41] emma: what bug are you trying to file? [04:41] For most people, it will be just making the experience of trying to file a bug even harder. [04:41] Hellow: ?? [04:42] Hellow: it's to prevent having to ask for information we need anyways [04:42] micahg, A "Before you file a bug, please read http://url" line at the top of the bug filing page would have been better. [04:42] this was it saves the triagers time [04:42] Hellow: no, because people ignore it [04:42] we want people to use ubuntu-bug [04:42] CarlFK: i just read through the page it redirects me to. The message i'm getting is that they don't want me to file bugs on Launchpad anymore. [04:43] emma: the bugs still get filed on lp - run ubuntu-bug, it collects info and uploads it as attchmetns to what you find on lp [04:44] CarlFK: I see. [04:44] either ubuntu-bug or the report a bug link in each program [04:44] assuming it actually finishes collecting info. I am about to file a bug against u-bug [04:44] CarlFK: apport-gtk never popped up? [04:45] ubuntu-bug xserver-xorg-video-nouveau = "Collecting problem information ... This might take a few minutes. ............." it just filled the 80x25 screen with 2000 dots, at about 1/2 sec per is 15 minutes. I have never seen it take this long. [04:45] Another option would have been a page directly after clicking "File Bug" or whatever it is that says "Before you file a bug on Launchpad, please read url" then "If you have read that page and wish to continue with filing a bug, please press button at the bottom of the page". [04:45] except it has now filled a 80x50 term window, still dotting..... [04:45] Instead of a hard link to the Ubuntu Community Documentation page. [04:45] s/link/redirect [04:45] CarlFK: Then the message I'm getting is that Canonical has created a launchpad which is not human readable/writable. [04:45] CarlFK: I'd say CTRL-C it and try again [04:46] emma: incorrect... just roll with it for now [04:46] Okay [04:46] emma: you can't critized it like this till you have tried it. then you can, and it will make more sense :) [04:47] micahg: im going to try to submit a bug report on irssi. [04:47] emma: ah, so, ubuntu-bug irssi [04:48] alright. [04:50] I also just noticed a bad flaw with wanting everyone to use ubuntu-bug: Quite a few people who use Launchpad don't use Ubuntu or Debian. [04:50] Hellow: ubuntu-bug is only for Ubuntu [04:51] Hellow: non http://bugs.launchpad.net/ubuntu/* pages accept bugs through the web interface [04:51] only ubuntu paths tell you to go use ubuntu-bug [04:51] maco, Ah, thanks. I didn't know that one. [04:54] is it OK to have /n in a translated string? [04:54] _('The collected information can be sent to the developers to improve the\n' 'application. This might take a few minutes.')) [04:55] CarlFK: idk [04:56] Package ubuntu-bug does not exist [04:56] what package is it in? [04:57] apport [04:59] CarlFK: what bug are you filing against ubuntu-bug? [04:59] that it is taking so long [04:59] CarlFK: did you retry? [05:00] not yet [05:00] Can somebody verify that anyevent-perl is really a duplicate of libanyevent-perl and then requesting removal? See also #470560. [05:02] https://bugs.launchpad.net/ubuntu/+source/irssi/+bug/493048 [05:02] Is that a good bug report [05:02] ^ [05:03] emma: looks good [05:03] #397140 [05:03] bug 397140 [05:04] ubot4: bug 397140 [05:04] ugh [05:04] I am not having a good bug day [05:06] CarlFK: micahg the ubuntu-bug thing is not as bad as i thought it was. Being redirected to a page that is written in a way that makes me wonder if I am being repremanded is not good though. I hope someone reconsiders that or at least changes the wording. [05:08] emma: my feelings exactly. [05:15] according to strace... [05:15] gettimeofday({1260076377, 725769}, NULL) = 0 [05:15] select(0, NULL, NULL, NULL, {0, 16000}) = 0 (Timeout) [05:16] aburch: looks like a duplicate package, I'll look into it a little later [05:22] micahg: ^c, re-ran... still collecting... [05:22] CarlFK: ugh, yeah, strace + ubuntu-bug apport? [05:23] https://bugs.edge.launchpad.net/ubuntu/+source/apport/+bug/493050 [05:25] micahg: apport having an issue? [05:25] nigel_nb: idk, CarlFK was [05:25] small world, I was just reading his report [05:27] CarlFK: just FYI, it works fine for me [05:28] for me too [05:28] it worked for apport :) [05:28] you're getting timed out? [05:29] strange [05:29] i'm not an expert at debugging though [05:30] so I ran it with xforwading, and got the gui "collecting..." dialog - hitting cancel does not stop it [05:32] I've no clue, we'll have to wait and see [05:34] micahg: does this bug qualify to be confirmed as there is enough info? [05:35] nigel_nb: I think confirmed means you can confirm [05:35] triaged would mean enough info even if you can't confirm [05:35] ah [05:35] I can't set it then [05:37] <^arky^> hi micahg [05:38] hi ^arky^ [05:40] <^arky^> howz is it going over there in windy city micahg [05:40] ^arky^: ok [05:40] <^arky^> have you seen jcostro around ? [05:40] * ^arky^ needs to renew his bugsquad membership [05:40] ^arky^: it's the weekend [05:40] ^arky^: bugsquad is open, you mean bug-control [05:40] <^arky^> yes [05:41] ^arky^: might have to wait until monday, don't know if any admins are on over the weekend [05:42] <^arky^> ok, I leave a message on lp then [05:54] anyone on irssi? [05:57] yes [05:58] dtchen: how do u change windows? [05:58] hold on, I'll give u the bug number [05:58] for buffers 1-10, meta+# [05:58] or, /win # [05:58] bug 493048, https://bugs.launchpad.net/ubuntu/+source/irssi/+bug/493048 [05:58] (10 -> 0) [05:59] using the /join command is not supposed to change windows if I'm not mistaken? [06:00] it does here [06:01] what i mean is if u are in channels a,b,c [06:01] does using join again change windows? [06:02] yes, it does [06:02] it works just fine for me in Hardy, Jaunty, and Karmic [06:02] okay, so its my ignorance that I can't reproduce it [06:02] both joining a new channel and switching to an existing (already-joined) channel [06:03] oh [06:03] when i'm using it [06:03] all new channels come like a new horizontal bar [06:03] thats normal? [06:03] no [06:03] should be a new number on the horizontal bar [06:03] though of course your .irssi/config has an effect [06:03] since it's what determines your layout [06:04] great [06:04] why is my default like this, grr [06:04] I should be clear that I'm using hardy-security/updates, jaunty-security/updates, and karmic [06:05] (so, 0.8.12-3ubuntu3.1, 0.8.12-6ubuntu1.1, and 0.8.14-1ubuntu1, respectively) [06:05] i think my issue is something at my end [06:05] but I got the bug confirmed [06:06] when u use /join to switched to an already joined channel, the extra space is creating problems [06:08] maco: feeling better? [06:08] yes thanks [06:08] and you? [06:08] very odd; I cannot reproduce that symptom on any of these [freshly created] users [06:09] http://dev.personnelware.com/carl/a/guid_mountpoint.png using the guid for the window title seems odd. is this worth filing a bug against? [06:09] maco: I'm frustrated and sleepy, and nursing a headache [06:10] CarlFK: yes [06:10] CarlFK: if you feel that the UUID is distracting, yes, please file a bug [06:10] package? [06:10] CarlFK: my geuss is it's already filed, but please check [06:10] nautilus? [06:10] micahg: yes - I filed it :) [06:10] CarlFK: gnome? [06:12] irssi bugs should be filed upstream? [06:14] yep: http://bugs.irssi.org/ [06:15] hm, singing up [06:15] oops, signing up [06:32] irssi upstream has a very odd interface [06:34] micahg: just a confusion [06:35] bug 493048, is a bug or feature request (my instincts say bug) [06:37] nigel_nb: low priority bug [06:38] thanks, the upstream version lets me select all this (i'm surprised though) [06:38] i mean the upstream tracker [06:39] * micahg never played with flyspray [06:43] micahg: flyspray cannot be tracked by launchpad? [06:44] nigel_nb: idk [06:45] not able to link it up [06:45] nigel_nb: not on the list https://help.launchpad.net/Bugs/RemoteTrackerCoverage [06:45] nigel_nb: jsut add a note in the bug [06:45] did that [06:45] been playing around for quite some time [06:45] flyspray is a terror [06:45] https://bugs.edge.launchpad.net/malone/+bug/28738 [06:46] first it sent confirmation mail to my spam box [06:47] anything i can do there? [06:47] nigel_nb: nope [06:47] nigel_nb: unless you want to write the code for LP :) [06:48] I'll pass [06:48] I can't edit gcalctool's code [06:54] micahg: once reported upstream, we leave the original bug alone? [06:54] in confirmed, undecided? [06:55] nigel_nb: I should mark triaged [06:55] hold on [06:55] oh, thanks :) [06:57] nigel_nb: done [06:57] :) [07:43] I am working on a bug (#394373 ) and would like to know the proper steps to take in order to close it. [07:44] URL? [07:46] https://bugs.launchpad.net/ubuntu/+source/qalculate-kde/+bug/394373 [07:46] what_if: what's the question? [07:47] what_if: first, you don't assign yourself a bug unless you are working on a fix [07:48] What to do now. A fix was released withthe newer packages, so I set the status to "Fix Released", but does this close the bug or must I nominate for a release? [07:48] nominate for release if you want it in a previous release [07:49] So assigning the bug to myself was incorrect in this case? [07:49] yes [07:49] you should subscribe if you want to keep up to date [07:51] who then would I notify that a bug has been fixed and released, but that nobody updated the launchpad entry? [07:53] what_if: no one, you should note the version that it's fixed in and marked fixed released if it's a confirmed bug, if it's an unconfirmed bug, mark as invalud [07:53] invalid [07:53] ubot4: status [07:53] Factoid 'status' not found [07:53] ubot4: Status [07:53] Factoid 'Status' not found [07:53] what_if: https://wiki.ubuntu.com/Bugs/Status [07:56] apologies... I have been assigning bugs to myself as a way to track them and assumed this was the proper way to do things. [07:57] that said, I have one more assigned bug. https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/206176 [07:59] that is also on it's way to being closed. Thank you for all your help, I'm still learning the way things are done in launchpad. [08:15] what_if: no, you don't assign if you're not making a patch [08:15] you can ask a question and subscribe [08:16] ok, I unassigned myself. Won't do that in the future. :) [08:16] what_if: you should probably talk to #kubuntu-devel about this bug, their new policy is to close bugs that are upstream [08:17] thanks for helping out though what_if [08:17] what_if: if you have a special interest in KDE, you should definitely talk to #kubuntu-devel [08:18] YW. This is why I'm starting out with such simple bugs, until i "learn the ropes" [08:18] what_if: have you read the initial documentation on how to triage [08:19] in here we don't actually "fix" bugs, but get them into the hands of those that can fix [08:19] what_if: https://wiki.ubuntu.com/Bugs/HowToTriage [08:23] I have... but am reluctant to invalidate this bug as a "read the manual" problem until I get a response back that my proposed solution fixes the problem the users are seeing. [08:23] was also reluctant to set it to confirmed, as from here it seems to just be an issue of a change in the way the Kate program operates. [08:24] what_if: triaged means that it's ready for a developer to look at [08:24] what_if: if you want to "triage" bugs, you should focus on New, Incomplete, and Confirmed [08:25] what_if: if you want to make patches/fixes, then this is the wrong channel === mac_v_ is now known as mac_v [08:26] what_if: I'm not trying to discourage you, but just explaining that we have different teams for these things [08:26] I am assuming ubuntu-devel is for patches/fixes? [08:26] what_if: no, that's for development discussion, #ubuntu-motu is for patches/fixes [08:27] what_if: but that bug, you need to talk to #kubuntu-devel [08:28] ok, I will get with the kubuntu-devel people about the process for this bug. Thank you again for all the help. [08:32] why "report a bug" link redirect me to the wiki? [08:32] why does* [08:35] damagednoob: because we have a process for reporting bugs [08:36] okay [08:36] i'm trying to file a "needs packaging" bug [08:36] what's the process for that [08:37] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages [08:37] "To get a package into Ubuntu, please file a bug in Launchpad" [08:37] damagednoob: there's a link there that will work [08:40] aaah got it [08:40] i have to join the bugsquad team first [08:41] damagednoob: to do what? [08:41] to report a bug [08:41] damagednoob: no you don't [08:41] well it's working now and it wasn't before [08:41] Is there any rationale why Ubuntu restricts changing the priority of bugs to members of ubuntu-bugcontrol when anybody can mark a bug as invalid/fixed/...? [08:41] damagednoob: where does it say that? [08:42] In Debian it seems to work quite well without any access restrictions. [08:42] https://wiki.ubuntu.com/MOTU/Contributing -> Preparing New Packages [08:42] aburch: I'm sure there is, but I don't know offhand [08:42] damagednoob: that's if you want to package something [08:43] micahg, it doesn't matter what anything says, i'm saying what happened [08:43] I would like to set priority for packages that I maintain in Debian, but first launchpad silently drops my mails to the bugcontrol mailing list, then I forgot about it for a while. [08:43] i couldn't file a bug until i joined the bug squad [08:43] aburch: we use the priorities to determine what to work on, and ubuntu is more of an everyone OS than debian is [08:43] damagednoob: I don't think that's the case [08:44] damagednoob: I think that was coincidence [08:44] micahg, okay [08:44] aburch: it prevents people from setting their issues to High because they want it fixed and distracting the developers, I would think [08:45] aburch: that's also across all of launchpad, not just ubuntu [08:46] Now I actually managed to send a mail to the list, but nobody relied (for 3 weeks). [08:46] aburch: https://help.launchpad.net/Bugs/Statuses [08:46] aburch: which list, for whast? [08:47] micahg: Everybody can change severity (the equivalent of importance) in the Debian BTS. It does not seem to cause many problems. [08:47] micahg: The ubuntu-bugcontrol mailing list. [08:47] aburch: debian is mainly used by sysadmins and power users, ubuntu is used on the desktop [08:48] aburch: that was right before UDS, please send a followup message and someone should reply this time [08:49] I see your message [08:49] aburch: in the mean time, you can ping someone in here and we'll be happy to set the importance for you [09:00] Ok. [09:01] Could somebody set 237233 to wishlist (feature request), 424404 to wishlist (feature request). [09:02] aburch: yep :) [09:02] aburch: is it triaged, do you have all the info you need? [09:03] While 312051 is already fixed (in Debian unstable), should bugs like there be low or medium in Ubuntu? [09:03] IMO giving wrong results (i.e. scheduling a job at the wrong time) is not so nice ;) [09:04] aburch: fix committed is if we have a fix in the archive [09:04] aburch: I'll set that one to high [09:05] micahg: Hmm? If the fix is in the archive, shouldn't that be fix released? [09:05] is it in Lucid? [09:05] No, only in Debian Sid and the VCS. [09:06] nope, not in lucid [09:06] yeah, so that's triaged still [09:06] aburch: we're syncing from testing this round [09:08] aburch: BTW, if you can include the LP bug # in your changelog in addition to the debian bug if you have it, LP will automatically close bugs that are in packages that are sync'd [09:08] aburch: nm, I see you already do :) [09:09] micahg: The first two bugs have all required information, it's just missing time to actually fix them ;) [09:09] aburch: midi music bug is wishlist? [09:11] micahg: I see it as a feature request (changing features enabled at compile time). [09:11]