Version: 0.8.0 (using KDE 4.7.2) OS: Linux From time to time the complete rekonq UI hangs for some seconds. This does not happen on a special site or when using flash etc … don't know what causes this. When launching rekonq via konsole I often get rekonq(16527)/kio (AccessManager) KIO::Integration::CookieJar::cookiesForUrl: Unable to communicate with the cookiejar! Reproducible: Sometimes Steps to Reproduce: Browse. Expected Results: No hanging UI ....
I can confirm this, with 0.8.0 (KDE 4.7.3 in kubuntu 11.10) Last lines when this happens in the console: -- (rekonq:7032): Gdk-CRITICAL **: IA__gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (rekonq:7032): Gdk-WARNING **: /build/buildd/gtk+2.0-2.24.6/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window QFont::setPixelSize: Pixel size <= 0 (0) rekonq(7032)/kio (AccessManager) KIO::Integration::CookieJar::cookiesForUrl: Unable to communicate with the cookiejar! --
*** Bug 273699 has been marked as a duplicate of this bug. ***
The same seems to happen with me as well. (rekonq 0.8.0 on KDE SC 4.7.2 on openSUSE 12.1)
So, WHY is this happening? The answer on the next chapter...
Eagerly awaiting for the next chapter, then ;) For what it's worth, it's also happening in KDE SC 4.8 RC2.
Dawit, can these be related?
(In reply to comment #6) > Dawit, can these be related? It can. The fact that the call to the cookiejar fails can definitely be the cause hang up since those calls are blocking DBUS calls and since the calls are invoked from the main GUI thread, it can definitely cause the app to freeze if the calls do not return immediately. The main issue here actually is why those calls are failing in the first place ? Did you upgrade to the most recent version of KDE and never logged out and logged back in for example ? If so, does doing that stop that warning message from being printed out ? If not, then you need to check and see if the cookiejar kded module is running correctly by manually issuing the following commands from konsole: qdbus org.kde.kded /modules/kcookiejar The above command should spit out all the available functions to call. If you do not see that and get an error message instead, then there most definitely is something wrong with your installtion. If the above works, then issue the following commands qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" "Set-Cookie: a=b" -1 qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" The first "listCookies" should spit out "Cookie: a=b", but the second one should simply print a blank line.
> The main issue here actually is why those calls are failing in the first place > ? Did you upgrade to the most recent version of KDE and never logged out and > logged back in for example ? If so, does doing that stop that warning message > from being printed out ? I am experience this behaviour for half a year or so (maybe even since kubuntu 11.04), so a temporary state is not the case >qdbus org.kde.kded /modules/kcookiejar Looks okay - like you have described it, 21 methods are listed >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" "Set-Cookie: a=b" -1 >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" > >The first "listCookies" should spit out "Cookie: a=b", yep >but the second one >should simply print a blank line. yep
(In reply to comment #8) > > The main issue here actually is why those calls are failing in the first place > > ? Did you upgrade to the most recent version of KDE and never logged out and > > logged back in for example ? If so, does doing that stop that warning message > > from being printed out ? > I am experience this behaviour for half a year or so (maybe even since kubuntu > 11.04), so a temporary state is not the case > > >qdbus org.kde.kded /modules/kcookiejar > Looks okay - like you have described it, 21 methods are listed > > >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" > "Set-Cookie: a=b" -1 > >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" > >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" > >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" > > > >The first "listCookies" should spit out "Cookie: a=b", > yep > > >but the second one > >should simply print a blank line. > yep Hmm... Then do you see the same error message being printed out if you use Konqueror with the "webkit" browser engine ?
On Sun, Jan 29, 2012 at 6:30 PM, Dawit Alemayehu <adawit@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=284959 > > > > > > --- Comment #9 from Dawit Alemayehu <adawit kde org> 2012-01-29 17:30:59 --- > (In reply to comment #8) >> > The main issue here actually is why those calls are failing in the first place >> > ? Did you upgrade to the most recent version of KDE and never logged out and >> > logged back in for example ? If so, does doing that stop that warning message >> > from being printed out ? >> I am experience this behaviour for half a year or so (maybe even since kubuntu >> 11.04), so a temporary state is not the case >> >> >qdbus org.kde.kded /modules/kcookiejar >> Looks okay - like you have described it, 21 methods are listed >> >> >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" >> "Set-Cookie: a=b" -1 >> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >> >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" >> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >> > >> >The first "listCookies" should spit out "Cookie: a=b", >> yep >> >> >but the second one >> >should simply print a blank line. >> yep > > Hmm... Then do you see the same error message being printed out if you use > Konqueror with the "webkit" browser engine ? Errr... sorry to ask a maybe dumb question - but how do i do that? Using the webkit browser engine, that is.
On Sun, Jan 29, 2012 at 1:24 PM, Klemens Dickbauer <klemens.dickbauer@gmail.com> wrote: > On Sun, Jan 29, 2012 at 7:13 PM, Dawit A <adawit@kde.org> wrote: >> On Sun, Jan 29, 2012 at 12:34 PM, Klemens Dickbauer >> <klemens.dickbauer@gmail.com> wrote: >>> On Sun, Jan 29, 2012 at 6:30 PM, Dawit Alemayehu <adawit@kde.org> wrote: >>>> https://bugs.kde.org/show_bug.cgi?id=284959 >>>> >>>> >>>> >>>> >>>> >>>> --- Comment #9 from Dawit Alemayehu <adawit kde org> 2012-01-29 17:30:59 --- >>>> (In reply to comment #8) >>>>> > The main issue here actually is why those calls are failing in the first place >>>>> > ? Did you upgrade to the most recent version of KDE and never logged out and >>>>> > logged back in for example ? If so, does doing that stop that warning message >>>>> > from being printed out ? >>>>> I am experience this behaviour for half a year or so (maybe even since kubuntu >>>>> 11.04), so a temporary state is not the case >>>>> >>>>> >qdbus org.kde.kded /modules/kcookiejar >>>>> Looks okay - like you have described it, 21 methods are listed >>>>> >>>>> >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" >>>>> "Set-Cookie: a=b" -1 >>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>> >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" >>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>> > >>>>> >The first "listCookies" should spit out "Cookie: a=b", >>>>> yep >>>>> >>>>> >but the second one >>>>> >should simply print a blank line. >>>>> yep >>>> >>>> Hmm... Then do you see the same error message being printed out if you use >>>> Konqueror with the "webkit" browser engine ? >>> >>> Errr... sorry to ask a maybe dumb question - but how do i do that? >>> Using the webkit browser engine, that is. >> >> Lanuch Konqueror. Click on Settings->Configure Konqueror and make sure >> the "Default browser engine" is set to "WebKit". > > Okay, normally I use rekonq, whicht doesn't have such a setting. But > webkit seems its renderer anyway, because I have a section "WebKit" in > its settings dialog, right? > When I launch konqueror, I have just "KHTML" as an option in the > dropdown box for the standard webbrowser engine. Ahem. You do or you do not have the option to select "WebKit". I am confused by your response. Anyways, if "WebKit" is not one of the choices in the drop down box, then the kwebkitpart package is not installed in your system. Install that package and "WebKit" should be available.
On Sun, Jan 29, 2012 at 8:19 PM, Dawit A <adawit@kde.org> wrote: > On Sun, Jan 29, 2012 at 1:24 PM, Klemens Dickbauer > <klemens.dickbauer@gmail.com> wrote: >> On Sun, Jan 29, 2012 at 7:13 PM, Dawit A <adawit@kde.org> wrote: >>> On Sun, Jan 29, 2012 at 12:34 PM, Klemens Dickbauer >>> <klemens.dickbauer@gmail.com> wrote: >>>> On Sun, Jan 29, 2012 at 6:30 PM, Dawit Alemayehu <adawit@kde.org> wrote: >>>>> https://bugs.kde.org/show_bug.cgi?id=284959 >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> --- Comment #9 from Dawit Alemayehu <adawit kde org> 2012-01-29 17:30:59 --- >>>>> (In reply to comment #8) >>>>>> > The main issue here actually is why those calls are failing in the first place >>>>>> > ? Did you upgrade to the most recent version of KDE and never logged out and >>>>>> > logged back in for example ? If so, does doing that stop that warning message >>>>>> > from being printed out ? >>>>>> I am experience this behaviour for half a year or so (maybe even since kubuntu >>>>>> 11.04), so a temporary state is not the case >>>>>> >>>>>> >qdbus org.kde.kded /modules/kcookiejar >>>>>> Looks okay - like you have described it, 21 methods are listed >>>>>> >>>>>> >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" >>>>>> "Set-Cookie: a=b" -1 >>>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>>> >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" >>>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>>> > >>>>>> >The first "listCookies" should spit out "Cookie: a=b", >>>>>> yep >>>>>> >>>>>> >but the second one >>>>>> >should simply print a blank line. >>>>>> yep >>>>> >>>>> Hmm... Then do you see the same error message being printed out if you use >>>>> Konqueror with the "webkit" browser engine ? >>>> >>>> Errr... sorry to ask a maybe dumb question - but how do i do that? >>>> Using the webkit browser engine, that is. >>> >>> Lanuch Konqueror. Click on Settings->Configure Konqueror and make sure >>> the "Default browser engine" is set to "WebKit". >> >> Okay, normally I use rekonq, whicht doesn't have such a setting. But >> webkit seems its renderer anyway, because I have a section "WebKit" in >> its settings dialog, right? >> When I launch konqueror, I have just "KHTML" as an option in the >> dropdown box for the standard webbrowser engine. > > Ahem. You do or you do not have the option to select "WebKit". I am > confused by your response. Anyways, if "WebKit" is not one of the > choices in the drop down box, then the kwebkitpart package is not > installed in your system. Install that package and "WebKit" should be > available. I'm confused as well. :) I do not know the relationship of rekonq and konquerer in KDE SC. They are different programs, yes? And what I know, or at least hoped to know is .) rekonq uses WebKit .) konqueror uses KHTML Since I use rekonq (and the ticket refers to it as well) I do not think the config of konqueror has anything to do with it, has it now?
On Sun, Jan 29, 2012 at 3:07 PM, Klemens Dickbauer <klemens.dickbauer@gmail.com> wrote: > On Sun, Jan 29, 2012 at 9:01 PM, Dawit A <adawit@kde.org> wrote: >> On Sun, Jan 29, 2012 at 2:39 PM, Klemens Dickbauer >> <klemens.dickbauer@gmail.com> wrote: >>> On Sun, Jan 29, 2012 at 8:19 PM, Dawit A <adawit@kde.org> wrote: >>>> On Sun, Jan 29, 2012 at 1:24 PM, Klemens Dickbauer >>>> <klemens.dickbauer@gmail.com> wrote: >>>>> On Sun, Jan 29, 2012 at 7:13 PM, Dawit A <adawit@kde.org> wrote: >>>>>> On Sun, Jan 29, 2012 at 12:34 PM, Klemens Dickbauer >>>>>> <klemens.dickbauer@gmail.com> wrote: >>>>>>> On Sun, Jan 29, 2012 at 6:30 PM, Dawit Alemayehu <adawit@kde.org> wrote: >>>>>>>> https://bugs.kde.org/show_bug.cgi?id=284959 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> --- Comment #9 from Dawit Alemayehu <adawit kde org> 2012-01-29 17:30:59 --- >>>>>>>> (In reply to comment #8) >>>>>>>>> > The main issue here actually is why those calls are failing in the first place >>>>>>>>> > ? Did you upgrade to the most recent version of KDE and never logged out and >>>>>>>>> > logged back in for example ? If so, does doing that stop that warning message >>>>>>>>> > from being printed out ? >>>>>>>>> I am experience this behaviour for half a year or so (maybe even since kubuntu >>>>>>>>> 11.04), so a temporary state is not the case >>>>>>>>> >>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar >>>>>>>>> Looks okay - like you have described it, 21 methods are listed >>>>>>>>> >>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" >>>>>>>>> "Set-Cookie: a=b" -1 >>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" >>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>>>>>> > >>>>>>>>> >The first "listCookies" should spit out "Cookie: a=b", >>>>>>>>> yep >>>>>>>>> >>>>>>>>> >but the second one >>>>>>>>> >should simply print a blank line. >>>>>>>>> yep >>>>>>>> >>>>>>>> Hmm... Then do you see the same error message being printed out if you use >>>>>>>> Konqueror with the "webkit" browser engine ? >>>>>>> >>>>>>> Errr... sorry to ask a maybe dumb question - but how do i do that? >>>>>>> Using the webkit browser engine, that is. >>>>>> >>>>>> Lanuch Konqueror. Click on Settings->Configure Konqueror and make sure >>>>>> the "Default browser engine" is set to "WebKit". >>>>> >>>>> Okay, normally I use rekonq, whicht doesn't have such a setting. But >>>>> webkit seems its renderer anyway, because I have a section "WebKit" in >>>>> its settings dialog, right? >>>>> When I launch konqueror, I have just "KHTML" as an option in the >>>>> dropdown box for the standard webbrowser engine. >>>> >>>> Ahem. You do or you do not have the option to select "WebKit". I am >>>> confused by your response. Anyways, if "WebKit" is not one of the >>>> choices in the drop down box, then the kwebkitpart package is not >>>> installed in your system. Install that package and "WebKit" should be >>>> available. >>> >>> I'm confused as well. :) >>> I do not know the relationship of rekonq and konquerer in KDE SC. They >>> are different programs, yes? And what I know, or at least hoped to >>> know is >>> .) rekonq uses WebKit >>> .) konqueror uses KHTML >>> Since I use rekonq (and the ticket refers to it as well) I do not >>> think the config of konqueror has anything to do with it, has it now? >> >> Unlike reKonq, which is a webkit only based browser, Konqueror can be >> configured to use either khtml or webkit since it is a KPart based >> application. All one has to do is wrap the very same browser engine >> reKonq relies on, i.e. kdewebkit, with a KPart module. That is exactly >> what kwebkitpart does. Make sense ? >> >> And the reason for having you test whether or not Konqueror + webkit >> browser engine exhibits the same issue is to determine whether or not >> this issue is in the class that provides the cookie integration or in >> reKonq. Does that clarify things for you ? > > okay, fine. I should install package "libkwebkit1", and then switch to > WebKit in konqueror and test if it hangs as well. Correct? Ahh... "libkwebkit1" ?? That no longer exists. The package you want to install is named "kwebkitpart". The version should be 1.2.0. Anything eariler than that is too old.
On Sun, Jan 29, 2012 at 9:12 PM, Dawit A <adawit@kde.org> wrote: > On Sun, Jan 29, 2012 at 3:07 PM, Klemens Dickbauer > <klemens.dickbauer@gmail.com> wrote: >> On Sun, Jan 29, 2012 at 9:01 PM, Dawit A <adawit@kde.org> wrote: >>> On Sun, Jan 29, 2012 at 2:39 PM, Klemens Dickbauer >>> <klemens.dickbauer@gmail.com> wrote: >>>> On Sun, Jan 29, 2012 at 8:19 PM, Dawit A <adawit@kde.org> wrote: >>>>> On Sun, Jan 29, 2012 at 1:24 PM, Klemens Dickbauer >>>>> <klemens.dickbauer@gmail.com> wrote: >>>>>> On Sun, Jan 29, 2012 at 7:13 PM, Dawit A <adawit@kde.org> wrote: >>>>>>> On Sun, Jan 29, 2012 at 12:34 PM, Klemens Dickbauer >>>>>>> <klemens.dickbauer@gmail.com> wrote: >>>>>>>> On Sun, Jan 29, 2012 at 6:30 PM, Dawit Alemayehu <adawit@kde.org> wrote: >>>>>>>>> https://bugs.kde.org/show_bug.cgi?id=284959 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> --- Comment #9 from Dawit Alemayehu <adawit kde org> 2012-01-29 17:30:59 --- >>>>>>>>> (In reply to comment #8) >>>>>>>>>> > The main issue here actually is why those calls are failing in the first place >>>>>>>>>> > ? Did you upgrade to the most recent version of KDE and never logged out and >>>>>>>>>> > logged back in for example ? If so, does doing that stop that warning message >>>>>>>>>> > from being printed out ? >>>>>>>>>> I am experience this behaviour for half a year or so (maybe even since kubuntu >>>>>>>>>> 11.04), so a temporary state is not the case >>>>>>>>>> >>>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar >>>>>>>>>> Looks okay - like you have described it, 21 methods are listed >>>>>>>>>> >>>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar addCookies "http://www.foo.bar" >>>>>>>>>> "Set-Cookie: a=b" -1 >>>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar deleteCookiesFromDomain ".foo.bar" >>>>>>>>>> >qdbus org.kde.kded /modules/kcookiejar listCookies "http://www.foo.bar" >>>>>>>>>> > >>>>>>>>>> >The first "listCookies" should spit out "Cookie: a=b", >>>>>>>>>> yep >>>>>>>>>> >>>>>>>>>> >but the second one >>>>>>>>>> >should simply print a blank line. >>>>>>>>>> yep >>>>>>>>> >>>>>>>>> Hmm... Then do you see the same error message being printed out if you use >>>>>>>>> Konqueror with the "webkit" browser engine ? >>>>>>>> >>>>>>>> Errr... sorry to ask a maybe dumb question - but how do i do that? >>>>>>>> Using the webkit browser engine, that is. >>>>>>> >>>>>>> Lanuch Konqueror. Click on Settings->Configure Konqueror and make sure >>>>>>> the "Default browser engine" is set to "WebKit". >>>>>> >>>>>> Okay, normally I use rekonq, whicht doesn't have such a setting. But >>>>>> webkit seems its renderer anyway, because I have a section "WebKit" in >>>>>> its settings dialog, right? >>>>>> When I launch konqueror, I have just "KHTML" as an option in the >>>>>> dropdown box for the standard webbrowser engine. >>>>> >>>>> Ahem. You do or you do not have the option to select "WebKit". I am >>>>> confused by your response. Anyways, if "WebKit" is not one of the >>>>> choices in the drop down box, then the kwebkitpart package is not >>>>> installed in your system. Install that package and "WebKit" should be >>>>> available. >>>> >>>> I'm confused as well. :) >>>> I do not know the relationship of rekonq and konquerer in KDE SC. They >>>> are different programs, yes? And what I know, or at least hoped to >>>> know is >>>> .) rekonq uses WebKit >>>> .) konqueror uses KHTML >>>> Since I use rekonq (and the ticket refers to it as well) I do not >>>> think the config of konqueror has anything to do with it, has it now? >>> >>> Unlike reKonq, which is a webkit only based browser, Konqueror can be >>> configured to use either khtml or webkit since it is a KPart based >>> application. All one has to do is wrap the very same browser engine >>> reKonq relies on, i.e. kdewebkit, with a KPart module. That is exactly >>> what kwebkitpart does. Make sense ? >>> >>> And the reason for having you test whether or not Konqueror + webkit >>> browser engine exhibits the same issue is to determine whether or not >>> this issue is in the class that provides the cookie integration or in >>> reKonq. Does that clarify things for you ? >> >> okay, fine. I should install package "libkwebkit1", and then switch to >> WebKit in konqueror and test if it hangs as well. Correct? > > Ahh... "libkwebkit1" ?? That no longer exists. The package you want to > install is named "kwebkitpart". The version should be 1.2.0. Anything > eariler than that is too old. Huh? What's happening? I have no kwebkitpart... -- $ apt-cache search kwebkitpart $ --
(In reply to comment #14) [snipped] > Huh? What's happening? I have no kwebkitpart... > -- > $ apt-cache search kwebkitpart > $ Well you must be on Debian. That is a problem. They only seem to use something that was packaged and released. The only version of kwebkitpart that was released that way was over 2 years ago. Due to time constraints I have not created release packages for release for kwebkitpart. In fact the 0.9.6 release was done by another person that used to work on kwebkitpart back then. Anyhow, if you are on Debian or its dervative, you might as well forgot about what I suggested. v0.9.6 is completely useless and will not work correctly with more recent versions of KDE.
On Mon, Jan 30, 2012 at 12:54 AM, Dawit Alemayehu <adawit@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=284959 > > > > > > --- Comment #15 from Dawit Alemayehu <adawit kde org> 2012-01-29 23:54:24 --- > (In reply to comment #14) > [snipped] >> Huh? What's happening? I have no kwebkitpart... >> -- >> $ apt-cache search kwebkitpart >> $ > > Well you must be on Debian. That is a problem. They only seem to use something > that was packaged and released. The only version of kwebkitpart that was > released that way was over 2 years ago. Due to time constraints I have not > created release packages for release for kwebkitpart. In fact the 0.9.6 release > was done by another person that used to work on kwebkitpart back then. > > Anyhow, if you are on Debian or its dervative, you might as well forgot about > what I suggested. v0.9.6 is completely useless and will not work correctly with > more recent versions of KDE. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are a voter for the bug. > You are on the CC list for the bug. Thanx for the additional info. And yes, I am using a Debian derivative, that is kubuntu 11.10.
Cannot reproduce anymore, shall we close this bug ?
Yes, after kubuntu 12.04 I moved most of my frequently-used sites back from Firefox to rekonq, didn't experience the problems (mostly they were on gmail) anymore. Closing is okay for me. Thanks to the developers or the packagers of kubuntu for fixing this. ~klemens
happy you'll find this fixed. Closing as "worksforyou".